Plugin Author
Steve
(@steveatty)
No there isn’t. I could add it as an option but as inserts on happen on publish and in background cron jobs (like cache refresh and comment fetching) then it really shouldn’t be an issue unless there are performance problems with your database server…
What tool produces that output?
I noticed it took a lot of time. Maybe a glitch. Usually no issue.
I installed the New Relic agent. Is a nice tool! 🙂
https://newrelic.com/product/real-user-monitoring
Thanks for the reply.
Plugin Author
Steve
(@steveatty)
Pity they want things like my phone number….. or I’d sign up to try it
Which of their tools are you using?.
I signed up through a link from the settings of the w3 total cache, this way standard account is free and I got a free t-shirt. 🙂 The did not call me (yet) 😉
It’s realy a nice tool!! Gives a lot of insight info on possible performance issues..
https://dl.dropbox.com/u/620272/ScreenHunter_09%20Mar.%2006%2019.03%20Pim.jpg
Plugin Author
Steve
(@steveatty)
Then I’ll give it a go.
70ms isn’t that bad for a DB write – our AIX system at work running against an XIV does most of its oracle calls at about 30ms
OK. Thanks.
PS: You wont regret it. It’s pretty awesome stuff, the tools they provide.
( and now I am not affected with this company hehe)
Plugin Author
Steve
(@steveatty)
Hmm. shows my average insert time into the error logs is 27.7ms
It also shows that FB calls take on average 400ms!!
Ooooh, sounds like a FB API fail??
Plugin Author
Steve
(@steveatty)
Well thats just doing the access token swaps – which is one reason why I severely whittled down the number of calls that I was doing to it, especially after FB changed their token renewal policy 😉
FB provide API response time monitoring:
https://developers.facebook.com/live_status
but notice the complete lack of scale 😉
Like I said..nifty tool! 😉
