|
at peak times I am doing "dozens" of writes at once.
...When we had 450,000 records in the file, at peek times, we see the
writes queue up.
Insert speed should be independent of the number of rows in a table,
you're just dropping data on the end of a heap. Do you have a capture of
the actual SQL statement that ran to do the inserts? Also, how did you
see the writes "queue up"? If there is a table scan occurring during an
insert then I'd say it's reportable to IBM as a (severe) bug. But I
don't think that's the case, something else is going on. Perhaps you're
trying to get the next# to use as a max(#) or something like that?
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
