Re: Table as fifo

[Zsolt Kendi]

First of all I try'd like 2 years before change the key_buffer_size. The index file itself 30MB. Does not matter the key_buffer_size 4K or 100M the result are same. Looks like bulding the key buffer take equal resources like overhead of disk IO directed to ramdiks. But I cannot decide the value 4K or 8 better for diasable. The value 8 give more side effect or bug...

On smallest test config:

"How much RAM do you have? " 4GB
"How big is the ramdisk? " 1GB
"What is on the ramdisk? " The --datadir is directed to ramdisk. The log, pid, tmp, socket directed to other mount.

"SHOW CREATE TABLE -- your sketchy presentation of this leaves out important details."
[ code ]
| AA | CREATE TABLE `AA` (
`C1` int(11) NOT NULL DEFAULT '0' COMMENT '',
`C2` int(11) DEFAULT NULL COMMENT '',
`C3` int(11) DEFAULT NULL COMMENT '',
`C4` datetime DEFAULT NULL COMMENT '',
`C5` int(11) DEFAULT NULL COMMENT '',
`C6` int(11) DEFAULT NULL COMMENT '',
`C7` int(11) DEFAULT NULL COMMENT '',
`C8` bigint(20) DEFAULT NULL COMMENT '',
`C9` bigint(20) DEFAULT NULL COMMENT '',
`C10` int(11) DEFAULT NULL COMMENT '',
`C11` bigint(20) DEFAULT NULL COMMENT '',
`C12` varchar(255) COLLATE latin2_hungarian_ci DEFAULT NULL COMMENT '',
`C13` bigint(20) DEFAULT NULL COMMENT '',
`C14` varchar(255) COLLATE latin2_hungarian_ci DEFAULT NULL COMMENT '',
`C15` int(11) DEFAULT NULL COMMENT '',
`C16` int(11) DEFAULT NULL COMMENT '',
`C17` varchar(255) COLLATE latin2_hungarian_ci DEFAULT NULL COMMENT '',
`C18` varchar(512) COLLATE latin2_hungarian_ci DEFAULT NULL COMMENT '',
`C19` varchar(2048) COLLATE latin2_hungarian_ci DEFAULT NULL COMMENT '',
PRIMARY KEY (`C1`),
KEY `C2` (`C2`),
KEY `C4` (`C4`)
) ENGINE=MyISAM DEFAULT CHARSET=latin2 COLLATE=latin2_hungarian_ci COMMENT='' |
[ /code ]
All sensitive but unimportant information replaced or removed from code...