| My first stab at this would be that Sybase on VAX/VMS is writing the
data to disk for every update, Sybase on UNIX is writing to memory and
only flushing at the end (or maybe not at all!). This is the usual way
unix would be set up, writes are done to memory and periodically
flushed. Is this good or bad - if the system stays up its good, if the
system crashes give me the VAX every time.
Caveat:- I don't know this for a fact but it would be the first thing
I'd look into.
Andrew
|
| re .1: Doubtful, unless SYBASE parameters are set incorectly on VMS.
SYBASE uses the same buffer flush and recovery strategies on both
operating systems.
I don't know the raw CPU horsepower of the RS6000 in question but I
imagine its better than the 4000-60. General industry trends are that
CISC does MUCH better than RISC when comparing SPECint per TPS. So, one
might expect the 4000-60 to equal or outperform the RS6000. SYBASE runs
pretty well on VMS so I'm really surprised at the result. I'd have to
guess that its either (1) bad tuning on the VAX or (2) a bug.
Vis a vi your Rdb number, unless its an apples to apples comparison using
a fully tuned Rdb then I wouldn't even mention your number to anyone. My
guess is that Rdb on the 4000-60 would beat SYBASE on the RS6000 given
Rdb V4.1 and proper tuning (and the identical application).
Hal
Ps: I concur with you that SYBASE has little incentive to help the VMS
sale when they win either way. Still, given the magnitude of the
difference SYBASE is probably worried. For example, if you told SYBASE
that they were running this application an order of magnitude slower than
Rdb/VMS on the 4000-60 they might be scared we could use that result
against them elsewhere. That would motivate them to help solve your
customer situation and take away a competitive black eye for them.
|