MVBASE performance problems

Hi,

I'm running MVBASE 1.3.02 with the latest patchset.

Hardware is: Sun Fire x4200; Dual Opteron/Dual Core model 275 (2.2GHz),
Windows Server 2003 x64/Standard Edition, 16G RAM.

Okay, now that we have that established. Yes, I know that version of
MVBASE is old; and that it's a 32-bit process running on x64 Windows,
but the problem I will describe happened before, on older hardware.

We have ~130 user licenses, with "averages" of 80-90 users on the
system at any one time. Usually under these conditions we scoot along
at ~1-5% CPU usage with occasional spikes to 10-ish (or so). Then,
occasionally, something will bump that WAY up, and one core ends up
maxed, the next one pretty high, and the other two mostly idle....

I have noticed when I do a LISTLINES it can produce this behavior (it
also freezes my session sometimes when I do LISTLINES)...

MVBASE itself is serving these connections via its own internal telnet
mechanism. I wanted to know (since all patches have been applied),
could it be that MVBASE's internal telnet server code isn't up to par
for serving that many users? If I offloaded it to the Windows telnet
service (either the regular win32 one or the telnetd included in
services for UNIX), might that help?

Any other suggestions, given that at this time I cannot upgrade or
change the multivalue product I'm using? Any way to track the
individual threads within MVBASE and see which ones are causing
trouble...?

Thanks,
Gabe

.

Relevant Pages

  • Re: MVBASE performance problems
    ... Windows Server 2003 x64/Standard Edition, ... MVBASE is old; and that it's a 32-bit process running on x64 Windows, ... MVBASE itself is serving these connections via its own internal telnet ...
    (comp.databases.pick)
  • Re: mvBASE, again
    ... I have MVBASE 1.3 patchset 09 running on Windows Server 2003... ... The workstation component regularly stops working, ...
    (comp.databases.pick)
  • Re: Migration away from mvbase?
    ... Well, actually, mvBASE does let you write to the host O/S which is generally Windows, but it could write through the network to any file system. ... Where I used to work, this was the standard way to do a backup - automate the mvBASE backup to write a virtual tape file at 11.00 pm, and automate the Windows backup to save all the files on the server at 1.00 am. Worked great. ... I can't enlighten you on migration experiences, although that site is in the midst of a migration to UniVerse. ...
    (comp.databases.pick)
  • Re: Recovering mvBAse VMS file from a Drive
    ... Windows XP, old drive had Windows 98 on it. ... old drive but the .VMS file is intact on the old drive. ... - I can read the mvbase .VMS file off the drive when it is connected ... installed Mvbase on the new computer and created a data file of 1Gb. ...
    (comp.databases.pick)