Pawel (privately) wrote: > Hi, > > This is not a file corruption I think. > > Please try to observe memory allocation during runing this select. Use > MW42 -m -P<port_number_of_your_session> to monitor MemFree and MemUsed > values. Let us know what is behaviour (how they change). I guess that > you may notice pretty high MemFree. > > Please check also ulimit (process limits) and LDR_CNTRL in order to > validate if SIGSEGV does not come from exceeded limits. > I think it is just running out of memory. > (Finally) I think that change of malloc options should help you (try > with "export MALLOCTYPE=watson" or > "export MALLOCTYPE=buckets"). > Pawel,
Did you ever run your tests using teh Watson allocator? > The last undiscussed thing is a sense of running SELECT command on such > a big file ;) > Ye s- unless it is a SSELECT built into the application, a series of smaller more manageable index based KEY-SELECTS will be way faster and take up much less resource. You can sort the final item list if you really NEED to process items in sorted order (which most people don't). Jim --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
