>We actually went about doing this and managed to port all but the
>tools, which is a *LOT* of work. However, we found that the ported
>version was *SLOW*, much slower than the SunOs version. This could
>probably be remedied by optimizing the code, but it was more work than
>we really wanted to do.
Interesting to hear there are performance problems with
the toolkit under Solaris...
The toolkit software doesn't actually *DO* much -- 9/10 of
the code is logging and error checking; perhaps more than 9/10.
The remaining code is almost completely system-bound. The proxies,
for example, rely heavily on socket operations and select. I suspect
you're seeing a difference in operating system performance on basic
network operations. I don't know a way to improve that short of
rewriting the networking parts of the toolkit completely [and even
then, who knows!?]
With respect to the toolkit's being a lot of effort to port
to Solaris -- we're working on improving the situation for upcoming
versions. If anyone is actively working on porting toolkit code,
please contact me, and I'll get you a copy of the internal prerelease
to work from, so we'll be less out of sync.
mjr.
Follow-Ups:
|
|
