RE: IDS 7.30: a table with 150 extents

Posted in 2000

Martin, Wayne E. — Thu, 15 Jun 2000 13:05:03 -0400 — source: Informix-list mailing list archive (1991-1998)

That's the way 7.30 works with tables that have a lot of extents, but the database should assert fail at about 200 extents. Make the first extent as large as possible and unload reload the table to get back to < 20 extents. -----Original Message----- From: Alex Barilo [mailto:hash1024@yahoo.com] Sent: Thursday, June 15, 2000 10:14 AM To: informix-list@iiug.org Subject: IDS 7.30: a table with 150 extents Hi folks, I have this table: 4 million rows (at one point it had 17 mill), 700Mb and 151 (!) extents! It's not fragmented. I wasn't the one who designed it that way so please don't nail me for that. My question is: how come we don't see any performance problems? Is there optimal extents number for IDS 7.30 (like 8 for online 5)? Or is it just powerful box? Hardware: HP NetServer LH4, 4x PII Xeon 400Mhz, 2Gb RAM, 6 logical HDD's (12 physical, RAID 10) for dbspaces OS: SCO OS 5.0.5 Any ideas will be greately appreciated. Thanx! Alex. -- Before the accident, I could not even spell UNIX Sent via Deja.com http://www.deja.com/ Before you buy.