I kept an eye on memory and cpu usage for the three processes below, plus
the rate of output from the packet cluster. In our case I'm running all
the Writelog machines off a central, and separate, ve7cc cluster server.
Both Writelog machines (Multi-two) would start to see problems at the same
time, the Bandmap flickering being the prime indicator, and the rate
through the cluster server would be at what looked like a high point. None
of these apps shows an increase in memory usage, but bandma32.exe becomes
a serious cpu hog and takes the cpu to 100% followed closely by
wlognetdde.exe - each taking about 50% each and dragging the host computer
down to a dead crawl. These are all modern XP machines with plenty of
RAM. The only solution is to kill these three processes and start again,
or reboot the computers which we had to do several times. In the end we
ended up not loading the bandmap component at all but near the end of this
weekends CQWW when packet traffic peaked again we still had the same
problems with cpu consumption.
I tried running the Writelog telnet sessions separatly and independantly
but no diference.
Bandma32.exe
WriteL32.exe
WlogNetDde.exe
One solution would be to geographicaly filter out traffic coming through
the ve7cc cluster server software thus reducing the load on Writelog. Does
seem odd though as the volume of traffic, even at peak times, would be
insignificant even to an old Commodore 64.
Microsoft's network DDE, by the way, is buggier than a flea circus. I was
under the impression they where trying to get rid of it.
Dale Ve7gl
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|