Things have been great now for 5 days. Thank you I will look at that, but will leave it ruuning for a few more days yet.Originally Posted by turbopower
Napper
Things have been great now for 5 days. Thank you I will look at that, but will leave it ruuning for a few more days yet.
Napper
wow alot of replies.
i think im good to go. i realised that group assignments in cacheex are in reverse to normal usage.
i am keeping cachex users in separate unique groups for the time being, and only sharing my local cache not other cachex caches. as you dont know how old other caches are and try to keep my cache sending fresh cache to peers.
im using cccam and camd35 peers too. and a mixture of the 2 again on clients.
1 thing i have noticed from cachex is that there doenst appear to be a steady stream of hits from cache3. not sure if these are timing issues or not. through the enablestats optino you can see whats being sent to and from, so when a client hits the cache3 it'll hit local again and then maybe cache3 again etc. its never a constant cache3, cache3, cache3 hits.
cache stats is one sure way of filling your memory , only use this option when debugging .
sticking to your settings for groups its a good idea to rely on a manual setup.
play with your cache timing settings till you get constant cahce3 hits .
ye i used it for debuggging i no longer have it enabled.
are these the only cachex timing options?
cachedelay = milli-seconds value to delay cached requests, default:0
max_cache_time = seconds maximum time CWs resist in cache after 1st client request, the time must be 2 seconds highter than the parameter clienttimeout, default:15
max_cache_count = count maximum CWs in cache, default:1000
cacheexwaittime = milli-seconds cache waiting time in milli-seconds for cache exchange, default:50
cacheexwaittime = delay maximum wait time for a cache exchange entry in milli-seconds, default:50can anyone recommend some for more constant cache3 flow?
can anyone recommend suitable timings for constant cache3 hit if avaialable?
Yes these are the only global options.
Currently i have my settings like this: (others are defaults)
cachedelay = 25
max_cache_time = 7
max_cache_count = 7500
cheers
is there a reason you introduce a delay on cache requests?
yes, i don't know how effective it is, but;
User wants ECM
Oscam checks cache without waiting => no hit
25ms delay..
Oscam checks cache again => HIT
Thats the concept of delay, but i never experienced with the setting as i have good results right now (50% hit).
i'll give it a try see what happens
i cant reply to pms at the minute says i can only post 10messages every 1440 minutes? :(
Do some donation and you loose the ads and limitations
:/ doh! no way lol
Posting Permissions
Reply With Quote