Thanks for the diagnosis.
There’s no doubt I’m memory-gated here; I’ll dig around for DIMMs at home, and see what I can find. I may well be able to boost things to a full 2 GB.
Weirdly, though, I routinely run this box with several Chrome windows with multiple tabs each, Freemind (a java-based mind mapper that’s another real mem hog), and jEdit, a java-based programmer’s editor with a huge plugin for editing lilypond music files, which routinely brings up a PDF viewer–all concurrently. Hardly light use, yet sporting no performance issues other than being slightly underpowered in the CPU department.
Linux’s swap-memory system puts Windows to shame; I would never try these workloads on this hardware in XP or Win7. My use tends to be “bursty” rather than big-task CPU use, so if I, for example, kick off a jEdit/lilypond compile of a large music doc, or load a huge freemind file, I expect a brief sys slowdown, but both apps respond instantly to keyboard input when not in the middle of a “heavy” operation. Not bad for 4-to-6-year-old hardware.
The only application I use other than Scrivener that slows the box down appreciably is VirtualBox, which directly poaches RAM from the rest of the system. Even then, slowdowns are “bursty”: when first firing up the VM, or task-switching between VBox and another app, an obvious trip to the swap file and back. The consistent slowness of Scrivener in this environment tells me that either there’s way too much going on with every keypress, or there’s some sort of old, thunky compatibility layer being used to get around the age of my CPU, or something similar.
I’m new to the board, here: is this a place where the Scrivener for Windows dev guy(s) routinely read, or should I try to formulate some sort of official bug report?
Also, have any “official” system requirements for Scrivener for Windows/Linux ever been floated? Might be that I’m just not meeting the requirements for one or more of the libs being used.