Why is yushan (a.k.a. lalashan) slow?
It may be slow only for you, or only for you in a particular browser session, or a particular preview session. Or it may be slow for a particular project.
If you started a slow job in a particular preview session, and you know what you did wrong, it may work to bail on the preview session. Copy your edits, open a new version of the page, and start editing again (without doing whatever you did to make it too slow).
If you have an error on a complicated page, WW will try to make all of your targets making the error over and over, and wasting your time. Use the "disable make" directive to stop making after the file you are focused on, like this:
If it is doing something slow in the main part of your project (running or merging), you really do have to wait before working on that project.
Yushan itself could also be bogged down, but right now it is distributing jobs to different nodes, so this doesn't seem likely. Or one of our file systems might be full. There is some diagnostic information below.
Top shows a snapshot of the load each processor thinks it's under. Yushan dumps reports for each node every 15 seconds.
Here is the current summary of the report:
df shows whether our disks are full. All of these numbers should be <90%, or else feel free to tell us about it.
Simply clicking your browser's reload button may not update the snapshots above, because the wiki caches its pages.
How we make these files
We generate top.report from yushan, because that's the machine that's supposed to poll all the nodes, but it's not running the working wiki.
We have a directory
/home/dushoff/bin/cron/status that takes files from here. Root uses cron to "make repeat" in that directory once every minute.
This is the perl script that makes the summary