CWO4 Dave Mann <misterfixit@loveable.com> wrote:> > I've noticed since d/l and installing latest WINE that when I fire up an > application requiring WINE, the "wine-preloader" jumps to 1.7 Gigs in > VmSize. I have a 2.0 GB RAM system but this action by the pre-loader slows > everything down to a low crawl.You mean that after starting up eg winecfg, you have 1.7 gigabytes of free memory (RAM and swap combined) less? Daniel
CWO4 Dave Mann wrote:> Daniel Skorka wrote: > >> CWO4 Dave Mann <misterfixit@loveable.com> wrote: >>> I've noticed since d/l and installing latest WINE that when I fire up an >>> application requiring WINE, the "wine-preloader" jumps to 1.7 Gigs in >>> VmSize. I have a 2.0 GB RAM system but this action by the pre-loader >>> slows everything down to a low crawl. >> You mean that after starting up eg winecfg, you have 1.7 gigabytes of >> free memory (RAM and swap combined) less? >> >> Daniel > > In the list of processes Vm Size shows as 1,755,045; Perhaps I am mistaking > that reading for actual memory use? The empirical result is that the > system slows down quite obviously.The virtual memory is not real memory. Wine "reserves" a very large block of virtual memory for reasons that have something to do with guaranteeing that certain memory addresses that some Windows programs expect are available. But most of it will never actually be used, and it will never get pulled into real memory. The system should not slow down when using Wine, especially if you have 2GB of real memory, unless you already have the memory almost full with other programs. Running Wine on a system with only 500MB, Wine is still consuming 1.6GB of virtual memory. Both everything else still runs fine.
Duane Clark <dclark@akamail.com> wrote:> CWO4 Dave Mann wrote: >> In the list of processes Vm Size shows as 1,755,045; Perhaps I am mistaking >> that reading for actual memory use? The empirical result is that the >> system slows down quite obviously.For absolutely any application under wine? Daniel
CWO4 Dave Mann wrote:> > Ah, yes, I understand now. The question is now whether to have any other > programs running when I use wine. > > Ordinarily here is what my system is doing: > ...Nothing really jumps out at me there.> > I have all the different screens sitting there ready to be used. Maybe if I > were running a 2+ Ghz dual processor mobo it would be better? I built this > 750 Mhx box a few years ago and have grown attached to it ... but will look > for any excuse to build another "really fast box". How about 4 GB RAM and > 3.5Ghz dual processor mobo??Oh well, 750MHz is a bit slow these days (though it was fast not so long ago ;), so I don't know how much that will impact things. Actually, unless there is a good reason for it, the AMD Sempron motherboards can be obtained cheap these days (at least in the US). They run fast, and even (relatively) cool and quietly. I highly recommend them unless you really have a strong need for maximum processing power. If your disc drive is from the 750MHz era, spend the extra money to replace that too.
Den Wed, 26 Apr 2006 20:32:46 -0500 skrev CWO4 Dave Mann:> Joris Huizer wrote: > >> Daniel Skorka wrote: >>> Duane Clark <dclark@akamail.com> wrote: >>> >>>>CWO4 Dave Mann wrote: >>>> >>>>>In the list of processes Vm Size shows as 1,755,045; Perhaps I am >>>>>mistaking >>>>>that reading for actual memory use? The empirical result is that the >>>>>system slows down quite obviously. >>> >>> >>> For absolutely any application under wine? >>> >> >> You could try running "notepad" - `wine notepad` - which is part of the >> wine tools; if that's slow, that proofs wine's preloading itself is slow >> for some reason > > Going to a user terminal and executing 'wine notepad' brought up notepad in > about 7 seconds. >Maybe a little bit over one second here (1 GB RAM, P4 2.4 GHz). Mvh Kent -- Hard work may pay off in the long run, but laziness pays off right now.