disk cache behind IIS

36 views
Skip to first unread message

Tim Richardson

unread,
Feb 6, 2016, 9:24:08 PM2/6/16
to web2py-users
I have an app set up on Microsoft's IIS 8.5 which seems to use a process pool to handle requests.
I also have a scheduler.
Does it make sense to try to update the builtin disk cache via a scheduled process?
the cache is an attribute of current but in this setup, requests being served by different processes would not possibly have the same "current".
However, the disk cache is files on the disk. Is the disk cache shared among all requests regardless of which process is serving them?

Niphlod

unread,
Feb 7, 2016, 4:25:28 AM2/7/16
to web2py-users
if for "disk cache" you mean "cache.disk" yes, it's shared among processes .

Tim Richardson

unread,
Feb 7, 2016, 9:18:04 PM2/7/16
to web...@googlegroups.com

On 7 February 2016 at 20:25, Niphlod <nip...@gmail.com> wrote:
if for "disk cache" you mean "cache.disk" yes, it's shared among processes .

Thanks, cache.disk is what I meant. 


--
Tim Richardson

Tim Richardson

unread,
Feb 7, 2016, 9:19:01 PM2/7/16
to web...@googlegroups.com
I guess, for completeness sake, that cache.ram would not be shared among the IIS process pool.

On 7 February 2016 at 20:25, Niphlod <nip...@gmail.com> wrote:

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/ITR8lcsYNSg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Tim Richardson

Niphlod

unread,
Feb 8, 2016, 8:26:33 AM2/8/16
to web2py-users
nope, it won't

Niphlod

unread,
Feb 8, 2016, 8:26:53 AM2/8/16
to web2py-users
ps: for anything in production, go redis.
Reply all
Reply to author
Forward
0 new messages