Welcome to the Question2Answer Q&A. There's also a demo if you just want to try it out.
+1 vote
564 views
in Q2A Core by

Can someone tell the reason for "Other" mentioned here? Does it include the file access times?

Q2A version: 1.8
by
What do you use for hosting?
by
Not due to hosting. This is happening only for a custom page which is from a plugin and not Q2A fault. Just need to know the reason for 'Other'. And my hosting is AWS.

1 Answer

+2 votes
by
selected by
 
Best answer

I believe it includes everything outside the PHP code itself or MySQL. So it would include reading files from disk or network requests.

I’m not sure off the top of my head but I think the MySQL section only includes usage from Q2A functions (qa_db_*). So if a plugin calls MySQL using the native mysqli_* functions it may count in “Other” too.

By the way if you want to get detailed performance info I’d recommend trying the Xdebug profiler alongside webgrind (or kcachegrind). It will show you exactly which functions take the most time.

by
Thanks Scott. I suspect it is due to a large number of included css/js files.
by
+1
I don't think the CSS/JS would not be included, because it only counts the server side.

In other words the time spent generating the HTML output (Time To First Byte). Once the HTML starts being sent the timing is done so loading CSS/JS after that doesn't count.
by
Thanks Scott. That makes it easier. I'm reading a google doc file -- it must be the reason for slowdown.
by
Yes that sounds likely. What are you using to read the file? Are you fetching a URL or using an API? Maybe there are faster ways, or you could cache the file locally for a while.
by
Currently I'm fetching the URL. I think I can just store the contents in the database with periodic updates from the URL.
by
Just confirmed that it is indeed the URL fetch. Was a bad method :)
...