Recordsets vs. Arrays?

[SABmore]

Is there a performance advantage to parsing thru a recordset verus using an
array?

I'm currently trying to populate a listbox by returning data from my
database, then either parsing thru the recordset until I reach the EOF, or
putting the data into an array.

Thanks for your assistance.

[Mark J. McGinty]

Wow this was a really long thread! :-)

I got some info about the processor affinity thing:
Mark J. McGinty wrote:

When running on an SMP box, is there any way to determine which CPU is
executing your code? [...]
The thread's affinity mask as well as the ideal processor could
be retrieved with the NtQueryInformationThread native API function.
However, I do not know a way to get (in user mode) the thread's
soft affinity (which is used internally by the scheduler to "mark"
the last CPU a thread was executed on).

Actually I should mention what brought this up, I wrote a quickie COM
object to call QueryPerformanceCounters from within ASP, for
profiling purposes. [...]

Since the implementation of QueryPerformanceCounters may read a
counter from the CPU, does the system make sure it always reads that
counter from the same CPU?
No, it does not. Most implementations (depends on the HAL) simply
use the rdtsc assembly instruction to read the CPU-internal clock
count. However, as each CPUs gets the same clock signal, their
rdtsc values should also be same.

The QueryPerformanceCounter specs gives some more evidence: "On a
multiprocessor machine, it should not matter which processor is
called. However, you can get different results on different
processors due to bugs in the BIOS or the HAL."
So it depends on the machine...

Well, I suppose you can assume that a more or less recent SMP
machine has no such bugs in the BIOS or HAL.
[ Written by Daniel Lohman]
-Mark



"Mark J. McGinty" <mm******@spamfromyou.com> wrote in message
news:7ncee.15674$_K.4813@fed1read03...
"Chris Hohmann" <no****@thankyou.com> wrote in message
news:Od**************@TK2MSFTNGP15.phx.gbl...

We're not storing the timer in the Application/Session scope so I think
either model is fine. With regards to the absense of GetThreadAffinity
you mentioned earlier, I don't think it's necessary since on success,
SetThreadAffinity returns the bitmask of the prior thread affinity mask.

Yeah I saw that, but didn't feel really comfortable with altering such a
thing blindly (setting it to the process' affinity mask) within the
process space of a server app, just to find out what it was before I
changed it... didn't seem like a polite thing to do. :-)

-Mark