You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a handy tool for diagnosing problems and identifying bottlenecks but when using it on a site that might be on a small server instance or shared host it would be nice to ease off on the number of requests sent to the server while the TimeStack interface is open.
I did look at adding this function myself but haven't used Knockout JS before and haven't really got time to read up on it right now so just thought I would mention it on here.
The text was updated successfully, but these errors were encountered:
Turns out the bit of code I put in place did sort of work so I've forked, finished it off, created a new branch called "pause" where I've made my changes.
I'm not sure if it's a feature that is needed by many people. I know the requests every second only hit the server slightly but it still generates a load of logs etc.
My implementation still needs some work. I will see how I get on with this feature and if I use it. If it is useful then I will make the pause button indicate it's paused and probably add a text input to specify the update frequency. I'll probably need to look into Knockout JS a little before I tackle that.
I've forked the plugin as well and added basic implementation for file storage when persistent object cache isn't "detected". I was trying to debug degraded performance when memcached was installed and storing the profiling data in the object cache (memcache) didn't really work out in that situation. Also it's nice to be abel to use this plugin on a host that doesn't have a persistent cache.
Hey @WPsites, great stuff - I think the ability to pause is a valid one for sure. For changing the request frequency of the polling, not sure how best to have an option for that, whether it would be in the UI of timestack -- I guess that would be best. Let me know if you need a hand with your fork.
As for persistant data storing - Yes! I have run into this issue quite a lot. Firstly because I want to test how slow things are without persistant object caching (though you can use apc to do that) and also to test on a server with no object caching.
This is a handy tool for diagnosing problems and identifying bottlenecks but when using it on a site that might be on a small server instance or shared host it would be nice to ease off on the number of requests sent to the server while the TimeStack interface is open.
I did look at adding this function myself but haven't used Knockout JS before and haven't really got time to read up on it right now so just thought I would mention it on here.
The text was updated successfully, but these errors were encountered: