Oh, sorry my fault I had a cache.ram left in a select() sorry...
cache.disk seems to work correct :-o
Sorry.
On márc. 11, 16:03, mdipierro wrote:
> very odd. This is the function gluon/cache.py that is supposed to do
> the clearing:
>
> defclear(self, regex=None):
> locker = open(sel
very odd. This is the function gluon/cache.py that is supposed to do
the clearing:
def clear(self, regex=None):
locker = open(self.locker_name,'a')
portalocker.lock(locker, portalocker.LOCK_EX)
storage = shelve.open(self.shelve_name)
if regex == None:
Hm... After time I see that cache.disk.clear() isn't working with my
wsgi setup too :(
WSGIDaemonProcess web2py user=www-data group=www-data home=/usr/local/
web2py/ processes=5 maximum-requests=1
Need more testing to allocate the problem :-o
On febr. 26, 09:10, mdipierro wrote:
> The fact
Cache.ram is not "completely" useless in a multi processes. If your
caching the entire html output of your front page, then its faster to
have this cached in ram instead of on disk, but its not a big deal
since its ok for new threads to recreate the cache in this single
instance.
Also if your runn
Nice. TNX.
On febr. 26, 11:25, Graham Dumpleton
wrote:
> For a further explanation of different modes you can run application
> under with Apache/mod_wsgi read:
>
> http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
>
> Graham
>
> On Feb 26, 7:42 pm, mdipierro wrote:
>
>
>
> > it is no
For a further explanation of different modes you can run application
under with Apache/mod_wsgi read:
http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
Graham
On Feb 26, 7:42 pm, mdipierro wrote:
> it is not useless. It works of if you run only one wsgi process but
> cache lives onl
I see, thanks.
On febr. 26, 09:42, mdipierro wrote:
> it is not useless. It works of if you run only one wsgi process but
> cache lives only within the lifetime of the process.
>
> On Feb 26, 2:32 am, szimszon wrote:
>
>
>
> > Okay. It looks good now. Thanks for the prompt replay.
>
> > But if I
it is not useless. It works of if you run only one wsgi process but
cache lives only within the lifetime of the process.
On Feb 26, 2:32 am, szimszon wrote:
> Okay. It looks good now. Thanks for the prompt replay.
>
> But if I understand well than the cache.ram is useless all the time
> apache is
Okay. It looks good now. Thanks for the prompt replay.
But if I understand well than the cache.ram is useless all the time
apache is used?
On febr. 26, 09:10, mdipierro wrote:
> The fact is the web server may be restarting the process or running
> more than one process. Apache does the same. In
The fact is the web server may be restarting the process or running
more than one process. Apache does the same. In this case you should
use cache.disk, not cache.ram.
On Feb 26, 1:34 am, szimszon wrote:
> Hello!
>
> I wonder if somebody could it confirm:
>
> I have a db:
> --- cut
>
10 matches
Mail list logo
