Am 22.05.2012 13:52, schrieb Johan De Meersman: > ----- Original Message ----- > >> From: "Ananda Kumar" <anan...@gmail.com> > >> yes, Barracuda is limited to FILE_PER_TABLE. > Ah, I didn't realise that. Thanks :-) > >> Yes, true there is CPU cost, but very less. >> To gain some you have to loss some. > > I've only got it enabled on a single environment, but enabling it added about > 20% of a single vcore to the CPU usage. Very visible (and not problematic) > because that system isn't CPU-bound :-) Converting an existing table to the > compressed format did shoot the CPU through the roof, though. > > See http://www.tuxera.be/filestore/vefeuraxinie/mysql-cpu-year.png for an > interesting graph
interesting because i have here a dbmail-server with no CPU load and innodb with compression enabled since 2009 (innodb plugin in the past) [--] Data in InnoDB tables: 6G (Tables: 49) [--] Up for: 5d 0h 44m 10s (455M q [1K qps], 50K conn, TX: 36B, RX: 13B) [--] Reads / Writes: 90% / 10% [--] Total buffers: 4.1G global + 1.2M per thread (500 max threads) [OK] Maximum possible memory usage: 4.7G (54% of installed RAM) [OK] Slow queries: 0% (3/455M) [OK] Highest usage of available connections: 18% (93/500) [OK] Key buffer size / total MyISAM indexes: 128.0M/76.4M [OK] Key buffer hit rate: 98.6% (40M cached / 559K reads)
signature.asc
Description: OpenPGP digital signature
