⚡ limit the cache queries to some optimal numbers

[vikiival]

Setting limits to the cache queries:
Spotlight 400
Series 900

How did I get those numbers?

1. let's make some base counts

select count(*) from series; // 1572
select count(*) from spotlight; // 720

2. let's set some base metrics?

for series I care about collection who has at least 1 KSM in the volume

select count(*) from series where volume <= 1000000000000; // 794

for spotlight want to see artists that have sell something

select count(*) from spotlight group by sold > 1 // 180, 540 // 180 sold 0 or 1 item

to be safe with the numbers:
794 -> moved to 900 - in case we have more collections
540 -> if user is not in the first half than ngmi

[roiLeo]

I don't really know where this cache is used but I would prefer, if possible, to add a maximum number per page

[roiLeo]

• default ORDER BY volume DESC?
• hardcoded 900?

[vikiival]

#99 (comment)

[vikiival]

@roiLeo description

[vikiival]

cc @ma-shulgin 👀

[vikiival]

I don't really know where this cache

should be used for all KodaDot stats - spotlight - series - whales

[roiLeo]

should be used for all KodaDot stats - spotlight - series - whales

Can you explain it to me with a simple use case?

[vikiival]

This queries are already in use for routes /spotlight
/series

[roiLeo]

I still don't understand why you need to put a limit on cached query

[vikiival]

I still don't understand why you need to put a limit on cached query

Because cache query on full data took about 30 sec to calculate and server ran out of the memory check #97

[roiLeo]

When is the cache updated?
Why do we need full data?
If we send all this data to the client side there is a great risk of slowing down user experience

[vikiival]

Why do we need full data?

We dont need that :) that's why we implemented limit