Money and slow computers --- CPU's??

I've used MSMoney since 98. I'm currently using V2003 on a
computer that I built with a minimum speed CPU. I'm using Win98.
Many things in Money work great but sometime the program is very
slow!! I think I have everything turned off to gain a little
performance.

The box that MSM came in recommends a CPU speed of 300 mhz. As I
would like to update the CPU for one faster, I will appreciate
your comments relative to speed, especially from those using an
antique computer like mine.

Dick
Mon Feb 21 19:40:00 CST 2005

Money is likely to seem one of your slowest applications on any computer
hardware you apply to run it--even the fastest money can buy today. Granted,
on that machine, you might find it perfectly usable. Even on my 2.2 GHz
P4/1GB PC2700/RAID 0 disks, Money can sit for a minute or more of hourglass
entering Tax Estimator or Budget Planner. (Granted this is not much more
than an entry level machine today, but it's not three years old and would be
hard to double the performance of today, given the current failure of
Moore's law.) The M03->M04 file upgrade took 30 minutes (28 or so of
non-responding hourglass time) on my 300 MHz Celeron with 256 MB of memory.
If got worse from there.

<Use-Author-Supplied-Address-Header@[127.1]> wrote in message
news:B0002091113@mail21.cisp.com...
> I've used MSMoney since 98. I'm currently using V2003 on a
> computer that I built with a minimum speed CPU. I'm using Win98.
> Many things in Money work great but sometime the program is very
> slow!! I think I have everything turned off to gain a little
> performance.
>
> The box that MSM came in recommends a CPU speed of 300 mhz. As I
> would like to update the CPU for one faster, I will appreciate
> your comments relative to speed, especially from those using an
> antique computer like mine.
>

Leonard
Mon May 16 17:09:01 CDT 2005

I think I figured out why Money is so slow. My M04 on a 1Ghz machine with 256
MB memory also takes about 1 minute (sometimes more) for every change I make
in budget. Horrible performance, and I may make several changes, which can
put me working on a budget for nearly an hour just to refigure amounts during
some months.

I monitored memory performance in system monitor. Every time it was taking
so long the only performance counters that radically changed were the
processor and the demand zero faults/sec. Every time I made a move in the
budget or change anything in other areas of money that are tied into budget,
money is forcing a zeroing out of a significant portion of memory. My guess
is that the more data you are working with the longer it will take to zero
out portions of memory.
--

Leonard (Bones) McCoy


"Dick Watson" wrote:

> Money is likely to seem one of your slowest applications on any computer
> hardware you apply to run it--even the fastest money can buy today. Granted,
> on that machine, you might find it perfectly usable. Even on my 2.2 GHz
> P4/1GB PC2700/RAID 0 disks, Money can sit for a minute or more of hourglass
> entering Tax Estimator or Budget Planner. (Granted this is not much more
> than an entry level machine today, but it's not three years old and would be
> hard to double the performance of today, given the current failure of
> Moore's law.) The M03->M04 file upgrade took 30 minutes (28 or so of
> non-responding hourglass time) on my 300 MHz Celeron with 256 MB of memory.
> If got worse from there.
>
> <Use-Author-Supplied-Address-Header@[127.1]> wrote in message
> news:B0002091113@mail21.cisp.com...
> > I've used MSMoney since 98. I'm currently using V2003 on a
> > computer that I built with a minimum speed CPU. I'm using Win98.
> > Many things in Money work great but sometime the program is very
> > slow!! I think I have everything turned off to gain a little
> > performance.
> >
> > The box that MSM came in recommends a CPU speed of 300 mhz. As I
> > would like to update the CPU for one faster, I will appreciate
> > your comments relative to speed, especially from those using an
> > antique computer like mine.
> >
>
>
>

Dick
Mon May 16 18:16:20 CDT 2005

"Demand Zero Page Faults - these happen when a process first references
newly allocated virtual memory pages. These do not involve the pagefile at
all. Any process that does frequent memory allocations and de-allocations
will experience a significant number of Demand Zero Page Faults. Processing
these events is a very low overhead activity and does not indicate that
demand for memory has exceeded the amount of available RAM. Very high
Demand Zero Page Fault rates are quite common for some applications but this
by itself has little affect on performance. The design and implementation
of the application affects the rate of Demand Zero Page Faults the
application experiences, so this can not be changed by adding RAM or
reconfiguring the pagefile."

http://members.shaw.ca/bsanders/WindowsGeneralWeb/RAMVirtualMemoryPageFileEtc.htm

The actual zero-fill of blocks of memory should be blindingly fast, given
the memory bandwidth available on most recent vintage machines. One thing I
found is that Windows 2000 and higher pre-zeroes pages and keeps a cache of
them available. This would be a very easy slack task--not that there is much
slack when Money is running. Of course on my machine, BOINC runs as well.

I'd be curious whether query-intensive Jet operations showed the same
signature.

"Leonard" <Leonard@discussions.microsoft.com> wrote in message
news:61731CAA-9C6B-4A1C-BB3F-85431663546B@microsoft.com...
> I think I figured out why Money is so slow. My M04 on a 1Ghz machine with
256
> MB memory also takes about 1 minute (sometimes more) for every change I
make
> in budget. Horrible performance, and I may make several changes, which can
> put me working on a budget for nearly an hour just to refigure amounts
during
> some months.
>
> I monitored memory performance in system monitor. Every time it was taking
> so long the only performance counters that radically changed were the
> processor and the demand zero faults/sec. Every time I made a move in the
> budget or change anything in other areas of money that are tied into
budget,
> money is forcing a zeroing out of a significant portion of memory. My
guess
> is that the more data you are working with the longer it will take to zero
> out portions of memory.

Randy
Mon May 16 19:53:21 CDT 2005

I am running Money 2005 and previously 2004, and don't see any significant
delays on any activity I do, every thing is very fast. Some portfolio
activities, require online access to accounts, but even those updates are
quite fast (have broadband Internet connection).


"Dick Watson" <littlegreengecko@mind-enufalready-spring.com> wrote in
message news:%23rM$F1mWFHA.3996@TK2MSFTNGP09.phx.gbl...
> "Demand Zero Page Faults - these happen when a process first references
> newly allocated virtual memory pages. These do not involve the pagefile
> at
> all. Any process that does frequent memory allocations and de-allocations
> will experience a significant number of Demand Zero Page Faults.
> Processing
> these events is a very low overhead activity and does not indicate that
> demand for memory has exceeded the amount of available RAM. Very high
> Demand Zero Page Fault rates are quite common for some applications but
> this
> by itself has little affect on performance. The design and implementation
> of the application affects the rate of Demand Zero Page Faults the
> application experiences, so this can not be changed by adding RAM or
> reconfiguring the pagefile."
>
> http://members.shaw.ca/bsanders/WindowsGeneralWeb/RAMVirtualMemoryPageFileEtc.htm
>
> The actual zero-fill of blocks of memory should be blindingly fast, given
> the memory bandwidth available on most recent vintage machines. One thing
> I
> found is that Windows 2000 and higher pre-zeroes pages and keeps a cache
> of
> them available. This would be a very easy slack task--not that there is
> much
> slack when Money is running. Of course on my machine, BOINC runs as well.
>
> I'd be curious whether query-intensive Jet operations showed the same
> signature.
>
> "Leonard" <Leonard@discussions.microsoft.com> wrote in message
> news:61731CAA-9C6B-4A1C-BB3F-85431663546B@microsoft.com...
>> I think I figured out why Money is so slow. My M04 on a 1Ghz machine with
> 256
>> MB memory also takes about 1 minute (sometimes more) for every change I
> make
>> in budget. Horrible performance, and I may make several changes, which
>> can
>> put me working on a budget for nearly an hour just to refigure amounts
> during
>> some months.
>>
>> I monitored memory performance in system monitor. Every time it was
>> taking
>> so long the only performance counters that radically changed were the
>> processor and the demand zero faults/sec. Every time I made a move in the
>> budget or change anything in other areas of money that are tied into
> budget,
>> money is forcing a zeroing out of a significant portion of memory. My
> guess
>> is that the more data you are working with the longer it will take to
>> zero
>> out portions of memory.
>
>

Dick
Mon May 16 21:06:14 CDT 2005

Consider yourself fortunate. How much data do you have collected?

"Randy" <nospam@comcast.net> wrote in message
news:OZ0wTrnWFHA.2448@TK2MSFTNGP10.phx.gbl...
>I am running Money 2005 and previously 2004, and don't see any significant
>delays on any activity I do, every thing is very fast.