redis is useful for relatively high sets of relatively small data (i.e.
high number of keys, each holding not so really big data), for highly
concurrent access (think 10k), for a high number of operations on keys
(think 10M). I don't see the reason behind you wanting to use redis for
dumping 20
Great, thank you.
>> doesn't seem at all something you absolutely NEED redis to do
What alternative do you recommend to think about?
Serialize data into session? sqlite? ...?
I cannot access the data immediately in controller call (because response
of third party service + parsing is too slow).
doesn't seem at all something you absolutely NEED redis to do, but feel
free to use it.
You can use an RConn() instance throughout your entire app.
On Friday, April 22, 2016 at 8:53:09 AM UTC+2, Mirek Zvolský wrote:
>
> Thank you.
>
> What I need is heavy computing related to few users, they DON'
Thank you.
What I need is heavy computing related to few users, they DON'T share any
data.
User asks a query, some web service gives very long response,
and it is necessary to parse it maybe 20s.
In this time user can continue work include send next questions.
Finally user will receive info, wh
that machinery is only needed for a module that needs to be used within
web2py, as cache and session need (and should) use a single object per
class with namespaced keys. Also, there's really no point or any
performance benefit on using separate databases in redis, and they're
unofficially depr
5 matches
Mail list logo
