May 27 2017
03:01 AM archivist: seb_kuzminsky, jepler in the search it started at result 200 for me, silly default change to 1
06:38 AM archivist: btw reason is to reduce the length of the table scan, speed it up
07:53 AM -!- #linuxcnc-devel mode set to +v by ChanServ
09:42 AM jepler: https://emergent.unpythonic.net/files/sandbox/flo-monitoring.png
09:43 AM jepler: when the CPU/memory usage obviously changed markedly is when I disabled joomla's internal caching
09:43 AM jepler: archivist: I looked at the search page http://forum.linuxcnc.org/search/ I don't see the "200" you are referring to
09:43 AM jepler: "Jump to result number" is pre-filled with 0 which is silly, but actually searching starts at result 2.
09:43 AM jepler: er, result 1
09:45 AM jepler: 58 total queries >.2s so far, about 2.5/hour.
10:06 AM archivist: jepler, my first search started at 200 which is daft
10:06 AM archivist: I wonder if the start point is related to number of results
10:09 AM archivist: I picked a a word I thought would be popular, it was andypugh and that had 368 results
11:22 AM seb_kuzm1nsky: jepler: i guess those two IO spikes correspond to the two recent outages here: http://forum.linuxcnc.org/tmp/requests.png
11:23 AM seb_kuzm1nsky is now known as seb_kuzminsky
11:25 AM archivist: if each page is 30 ish requests then its struggling at 10 pages a minute...
11:27 AM archivist: if I am reading that graph and the counts off https://www.webpagetest.org correctly