Had this problem with cmucl src/code and src/compiler directories a while ago but it was fixed.
However, try getting the file list for ansi-tests/ansi-tests and scroll down a bit. It brings firefox to its knees. Chrome is a bit better but it still takes a while on my 3GHz imac.
Compare this with github.com/rtoy/ansi-cl-tests. It's very smooth and takes no time at all.
(It would probably be nice for its own sake if ansi-tests put related tests into subdirectories instead of all the files in one directory. But that's a different issue.)
-- Ray
Hi Raymond,
I'm not sure I'm seeing the same thing as you are. How long does it take for your display to be updated and how much CPU does it take (on how many cores)?
On my machine, I'm only getting a few percent CPU (with 4 hyperthreading cores) and the bottom of the page updates within a minute.
Regards,
Erik.
On Sun, Aug 30, 2015 at 4:17 PM, Raymond Toy toy.raymond@gmail.com wrote:
Had this problem with cmucl src/code and src/compiler directories a while ago but it was fixed.
However, try getting the file list for ansi-tests/ansi-tests and scroll down a bit. It brings firefox to its knees. Chrome is a bit better but it still takes a while on my 3GHz imac.
Compare this with github.com/rtoy/ansi-cl-tests. It's very smooth and takes no time at all.
(It would probably be nice for its own sake if ansi-tests put related tests into subdirectories instead of all the files in one directory. But that's a different issue.)
-- Ray
"Erik" == Erik Huelsmann ehuels@gmail.com writes:
Erik> Hi Raymond,
Erik> I'm not sure I'm seeing the same thing as you are. How long Erik> does it take for your display to be updated and how much CPU Erik> does it take (on how many cores)?
Erik> On my machine, I'm only getting a few percent CPU (with 4 Erik> hyperthreading cores) and the bottom of the page updates Erik> within a minute.
Ok, I think the test isn't quite right. Moving to the end is fast. What I was doing was a bit more complicated. Move to the end, then drag the scrollbar up towards the middle of the list. (You should do this in some area where the commit log for the file hasn't been updated.) Then use the mouse wheel to move around some more.
After doing this for a bit, I see both Chrome and Firefox use 100% CPU (8-core 4 threads/core i7 machine at work). Eventually, I see Chrome pop up a window that says the page is hung and Firefox pops up a window that says the script is unresponsive.
Curiously, after a while, the mouse wheel will scroll around but I can't drag the scrollbar at all. Perhaps these are bugs in Chrome/Firefox.
This will get fixed when ansi-tests moves things into subdirectories.
-- Ray
-
Erik Huelsmann -
Raymond Toy