[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On 1/6/2004, Melodie Frances wrote:

Does anyone have a recommendation for the actual amount of memory that is needed to run Millennium efficiently? The III recommendation does not work for us. We have on average 8-10 windows open at a time, about half of which are memory eaters.

Melodie,


The activities you are doing with the Millennium Java client will
affect how much real memory is used.  In my experience, Millennium
Circulation terminals seem to run fine on 64 MB or 128 MB if all
you are doing is performing checkin and checkout transactions (which
makes sense... all you are doing is passing a few bytes of data back
and forth between the client and the server).


Multi-function workstations are more of an issue, as other functions can require more real memory. In particular, I've found Millennium Create Lists can consume a fair amount of memory. On my workstation, I have had a few problems with 512 MB of RAM. (Although I will say, I never noticed a problem prior to Release 2002 Phase 3. I generally use either Millennium Circulation, but we're beta testing ERM so I sometimes run Millennium ERM or Millennium Serials).

I'm not sure if there is a memory leak in the latest release, but it
is a possibility I have considered recently.  Previously, I was
thinking along the lines of Andrew Hollingsworth, who suggested "rapid
development of programs and the [decreasing] cost of RAM" are more the
issue.  However, I have had to use the Windows Task Manager to kill
off Millennium clients on my workstation several times in recent
months when they hang or become non-responsive, consuming large
quantities of CPU and RAM.  I am almost always using Create Lists
when this happens, and it seems to happen after the Millennium
client has been open a while (suggesting some memory fragmentation
may be in play as well).

I'm planning to increase my workstation from 512 MB to 1024 MB or
2048 MB, but haven't had time to do so yet.  I'd like to see if it
might help alleviate the problems I've seen.

However, let me restate.  These problems are RARE, and 512 MB seems
to be more than enough memory under "normal" operating conditions.
(For me... NOC generally means 2-3 SSH terminal windows, several
web browser windows, occassionally two different web browser
applications, and one or two Microsoft Office applications all
concurrently open while I am using Millennium).

Your mileage may vary...


Oh, we run Windows 2000 Professional SP4 universally.


--

   Craig A. Summerhill
   Applications Development Librarian
   University of Nevada, Reno
   Getchell Library 174A / Mail Stop 322
   1664 North Virginia Street
   Reno, NV   89557-0042

      (775) 784-6500 x227
      <summerhi@xxxxxxxxxx>