Does MySQL require periodic reindexing for indexes on columns whose
value permanently increases (while the oldest entries are expired)?
Another database suffers from the so-called "creeping index syndrome",
which results in ever-growing indexes in such cases (some pages in the
index can never be r
I've got a table with 100 million rows and need some indexes on it
(one row is 126 bytes).
I'm currently using MyISAM and the indexing proceeds at an
astonishingly low rate: about 200 MB per hour. This is rate is far
too low; if we had to recover the database for some reason, we'd have
to wait fo
Konstantin Yotov <[EMAIL PROTECTED]> writes:
> 2x1GHz Intel, 1GB RAM, 40GB WD 7200 8MB cache.
> We are going to uprade our server but I'am wondering
> between new Opteron (1.4GHz)and Xeon (2.4).
Can't you get a machine for testing before you buy it? Xeon
processors aren't necessarily a signific
"Dathan Vance Pattishall" <[EMAIL PROTECTED]> writes:
> #use for when mysql is doing a check or repair
> set-variable= myisam_sort_buffer_size=64M
>
> to a higher value will make the index happen faster on the fly.
Oops. I only adjusted the key_buffer value. Probably I should set
myisam_sor
"Dathan Vance Pattishall" <[EMAIL PROTECTED]> writes:
> Maybe increasing
>
> #use for when mysql is doing a check or repair
> set-variable= myisam_sort_buffer_size=64M
>
> to a higher value will make the index happen faster on the fly.
MySQL doesn't seem to honour this variable. I've set it
"Brad Brad" <[EMAIL PROTECTED]> writes:
> The OpenBSD server is 2.8Ghz and may have as many as 230 mysql
> sessions with 14 queries a second, the rest will be sleeping (ftp
> sessions maintain connection). The db directory is 80mb total,
80 MB? Is this a typo?
> The old server is seems quite h
