| # |
Apr 19th 2017, 13:35 |
hmic |
yes, if the cache is not warmed up, first access will be slow. who cares? |
| # |
Apr 19th 2017, 13:35 |
inoas |
and then simply write the cache |
| # |
Apr 19th 2017, 13:35 |
inoas |
so you would actually let the requests hit the application |
| # |
Apr 19th 2017, 13:34 |
hmic |
so you use a cache! |
| # |
Apr 19th 2017, 13:34 |
inoas |
a fast read proxy |
| # |
Apr 19th 2017, 13:34 |
inoas |
because hitting the database is slow |
| # |
Apr 19th 2017, 13:34 |
hmic |
why do you? |
| # |
Apr 19th 2017, 13:34 |
inoas |
okay, then I want a proxy ;p |
| # |
Apr 19th 2017, 13:34 |
inoas |
https://github.com/makallio85/yaml-route doesn't get purged |
| # |
Apr 19th 2017, 13:34 |
hmic |
a cache is a cache and its not persistent by definition |
| # |
Apr 19th 2017, 13:34 |
hmic |
for you too! |
| # |
Apr 19th 2017, 13:34 |
inoas |
yeah that's not where I want to go |
| # |
Apr 19th 2017, 13:33 |
hmic |
it can get purged whenever |
| # |
Apr 19th 2017, 13:33 |
inoas |
read again, not for me |
| # |
Apr 19th 2017, 13:33 |
hmic |
ionas: it's a cache! |
| # |
Apr 19th 2017, 13:33 |
inoas |
redis continues to live |
| # |
Apr 19th 2017, 13:33 |
inoas |
hmic but APCu breaks down when you restart the webserver |
| # |
Apr 19th 2017, 13:33 |
crazycoder |
i should set _joinData hidden on the fly |
| # |
Apr 19th 2017, 13:32 |
hmic |
but the fastest i can get, which is php-process memory (APCu) followed by memcache |
| # |
Apr 19th 2017, 13:32 |
crazycoder |
$_hidden on entity works but i cannot change it globally. |
| # |
Apr 19th 2017, 13:32 |
crazycoder |
hey hmic! |
| # |
Apr 19th 2017, 13:32 |
crazycoder |
it is really really bad but if there is no alternative i should do that: https://gist.github.com/anonymous/3f55105fe22a4db8dd017285d140f383 |
| # |
Apr 19th 2017, 13:32 |
inoas |
Instead? Memcache? |
| # |
Apr 19th 2017, 13:31 |
hmic |
redis is a quite good cache for heavier things, i'd personally not use it for routes |
| # |
Apr 19th 2017, 13:30 |
inoas |
like https://github.com/makallio85/yaml-route but in redis |
| # |
Apr 19th 2017, 13:30 |
inoas |
redis would be not a simple cache but more like the router-storage |
| # |
Apr 19th 2017, 13:30 |
inoas |
and then build-cache-on-write |
| # |
Apr 19th 2017, 13:29 |
inoas |
I am considering: hit cache first, if not found, hit cake-stack? |
| # |
Apr 19th 2017, 13:29 |
hmic |
you can of course warm your cache up however you like... |
| # |
Apr 19th 2017, 13:29 |
inoas |
well but then it times out |
| # |
Apr 19th 2017, 13:29 |
inoas |
well "slow" in relative terms |
| # |
Apr 19th 2017, 13:29 |
hmic |
yes |
| # |
Apr 19th 2017, 13:29 |
inoas |
hmic so first hit = slow? |
| # |
Apr 19th 2017, 13:29 |
 nemmons |
our routes don't change that much so we don't have to worry about re-writing the cache. i think we refresh it like every 6 hours and also have an admin controller action to refresh manually if necessary |
| # |
Apr 19th 2017, 13:29 |
inoas |
are you using cakephp's RedisEngine? |
| # |
Apr 19th 2017, 13:29 |
hmic |
ionas: populate the cache when a route gets requested |
| # |
Apr 19th 2017, 13:27 |
inoas |
if a route isn't found, do you build it live/hot? queued? |
| # |
Apr 19th 2017, 13:27 |
inoas |
nemmons do you write the cache on edit? |
| # |
Apr 19th 2017, 13:27 |
inoas |
else I have to do database queries for every on-page object |
| # |
Apr 19th 2017, 13:27 |
nemmons |
ionas we use redis to cache routes loaded from the database |
| # |
Apr 19th 2017, 13:26 |
inoas |
I am thinking, JSON, XML, YAML, Redis |