just had a quick check of the 54624A update rate, and here are the relations to the timebase settings:
a: 5ns/div -> 360KHz update rate
b: 10ns/div -> 320K
c: 20ns/div -> 230K
d: 50ns/div -> 126.7K
e: 100ns/div -> 87.7K
f: 200ns/div -> 46.7K
g: 500ns/div -> about 2K
FYI
I found another 54620 series scope at school and made the measurements again. The Trigger out frequency was about 330kHz at 5ns horizontal setting. I am kinda confused. If my measurements were wrong, then I really do not know why. Well, it is a mystery for me.
While I realise this is rather necroposting, I just did a brief test on a 54622D myself, and I get 362kwps with a 25MHz sine wave and 5ns/div, otherwise default settings.
However, I should note that this is not realtime sampling, it is operating in equivalent time sampling mode at this timebase setting by default.
Overriding to realtime sampling decreases the update rate to only 4kwps.
The automatic switch between equivalent time to realtime happens between 200ns/div and 500ns/div.
The maximum I seem to be able to achieve in realtime, with the 'right' signal and timebase is 4kwps with vectors, and about 12.3kwps with dots.
On a related note, this scope is super self-explanatory and simple to use, the menus are also simple and clear. The UI is also super quick. It could so easily be a benchmark for other scopes when it comes to ease of use. If I compare it to the Tek TDS460a I have here, admittedly a couple of years older, it seems that HP/Agilent and Tek took two completely different paths regarding UI design in those days with the advent of the DSO. HP's was a sleek, ergonomic design, whereas Tek seems to have struggled at that time, with a UI that is difficult to navigate and painfully slow to respond.
The 54622D I picked up appears to have been in storage unused for some time. It is an HP refurbished unit, and from the condition of the complete probe set that came with it, it appears to have rarely, if ever, been used since. All the parts are there, and the channel identifying colour clips were not attached. When I first switched it on I had some trouble for a couple of hours with all the rotary encoders incorrectly registering, randomly going backwards and forwards as they were turned. After some vigorous turning backwards and forwards and a bit of time, a couple of hours later they were fine. It was a cold day, and I strongly suspect that judging from the screen condensation, the encoders had become temporarily contaminated too.
But yes, I can see why these puppies were so popular. These days, I think that the 54624A 4 channel analogue-only may be a better bet: I seem to use LAs only rarely these days, and before there were LAs, I used a scope anyway, even for 16 bit processors (that was indeed a lesson in patience debugging your software by probing the address and data lines with a scope!) The I2C triggers fine on the analogue channels, but regretfully there is no I2C decode, however for us old farts who've been doing I2C since the 80s it's not such a big deal, but the deep memory together with I2C triggering is very nice.
So,if you happen to come across one of these beauties at a reasonable price, you might just enjoy using it.