Duane Clark wrote: > CWO4 Dave Mann wrote: >> Daniel Skorka wrote: >> >>> CWO4 Dave Mann <misterfixit@xxxxxxxxxxxx> 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. -- 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: Screen # Application 1 KMail 2 KNode 3 Firefox on Home Page 4 Nothing (Used as a screen for user terminal work) 5 Limewire - Linux version 6 XINE - waiting to be used 7 Nothing (Used as a screen for Echolink on wine) 8 GAIM 9 MahJongg Game with Aztec Tiles full screen 10 RealPlayer (Linux version) active and XMMS waiting inactive 11 KOrganizer full screen 12 Web Schedule running on remote system 13 Nothing (Used for GNUCash and KMyMoney) 14 KDE System Guard Process Table with graphic display 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?? Cheers, Dave ~~~~~~~~~~~~~~~~~~~~~~~~ Study History - Know the Future _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
