We had to disable multi-threading sort as we were getting unable to create pipe errors on occasion and we were having problems with our indices.
We would do a BUIILD.INDEX ALL and one or more of the builds of an index would abort leaving the phantom hanging and all the other phantoms would hang up, making the whole process come to a standstill. We've not had either problem since we disabled it. We are on Redhat Linux running 10.1. Brenda -----Original Message----- From: Stevenson, Charles [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 9:52 AM To: [email protected] Subject: RE: [U2] UVTSORT config parameter Dear Messrs. Dreyfuss, Oliver, Wurlod, gurus all, My original request was for words of wisdom. History lessons count. The older I get, the more I value them. Thank-you. But I was more interested in the future (my own): - Why would I enable multi-threading? (UVTSORT 1) - Why would I disable multi-threading? (UVTSORT 0) - If "1" is always right, why did IBM make it configurable by the user? - What symptoms would make me suspect I have it wrong? - How would one test it? - Is there any documentation? Cherishing your every word, Chuck P.S. I'm anticipating upgrade to HP Itanium, HPUX11.23, UV 10.2.5. I assume multi-threading sorting applies there, although it wasn't stated. -----Original Message----- From: LeRoy Dreyfuss Thx Mr. Oliver. I recall our pal Pete Simonson telling me that some years ago. Just didn't want to stick my neck too far out without some caution :-) -----Original Message----- From: Clifton Oliver Yes. According to my conversations with DG, the project was referred to as "Firestorm" and had DG's affinity throughout. > Not sure, but I believe VMark had DG do the actual development for > affinity. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
