|
PureBytes Links
Trading Reference Links
|
I have been monitoring ts2000i to try and understand
more about how it works. Two broad observations.
Memory utilization is high. I would have at least
256 meg on any system, otherwise, you will swap
heavily. The number of libraries it is dependant on
is also very high. This is probably some cause of the
stability problems. It doesn't seem to leak memory.
If anybody else has been doing this and keeping information
on the crashes, in what library and the stack trace, we could
start to see if we can narrow down most of the problems to
specific areas. Hopefully this is the case and the problems
are not all over the place. This is important for us to collect
because when you talk to tech support at Omega, they do not seem
to be interested in the stack trace generated. Myself, this is the
first thing I want to know, and the second is what was the user
doing. The stack trace is a list of addresses that you can
match to function calls in the libraries, and you can walk the function
chain to see where the crash happened. If I have no other debug
information but the stack trace and what the user did, I will try
to reproduce the user's steps with breakpoints in the functions,
to try and find out what caused the crash. We don't have source code,
but at least we can find out how many of us are having crashes in the
same place. Hopefully Omega has gone a little further and has
allowed logging or other debug flags to be turned on, If so,
they should let us know.
Anyway, if people are willing, we should create a more specific
bug list with the stack trace information.
This is the result of some simple monitoring of
TS 4.0 vs TS2000i. These tests were done on a system running
Windows 98 with the latest Microsoft maintenance,
a 350 MHz Pentium II, with 256 Meg of memory.
The Ts2000i server runs 10 threads, and links in some 70+ dll's.
Ts2000i runs 3 executables (ts32.exe 5 threads, and 80+ dll's),
(ortrade.exe 1 thread, 80+ dlls), (orgtcc.exe 4 threads, 80+ dll's),
with ortrade.exe the parent of ts32.exe and orgtcc.exe. These are both
parented to explorer, parented to the msgserver, parented to the kernel.
The crashes are going to be in one of the dll's of the many above.
System at idle, nothing running but Windows 98
Processor usage 20%
86 Meg of memory allocated
TS 4.0
Offline server, 2 symbols in the portfoloio,
Processor usage 100%
94 Meg of memory allocated
Tradestation Active,
2 workspaces open, 1 symbol each doing nothing
Processor usage 100%
100 Meg of memory allocated
Ts2000i
Offline server, 1 symbol in portfolio
Processor usage 27%
138 Meg of memory allocated
Ts2000i active, 2 workspaces open 1 symbol each doing nothing
Kernel 27%
200 Meg of memory allocated
As a comparison, running Netscape with IQChart realtime both up and
active,
the memory usage is about 160 Meg, and the cpu utilization is about 30%,
collecting more symbol information than the Global server. IQChart has
never crashed on me, and Netscape does maybe once every couple of
months.
This isn't an apples to apples comparison, but shows a big application
like
Netscape running with a java based real time charting application, and
its
usage on the system.
Thanks,
David
|