… if there is a transaction that executed a query which opened that table. Bug fixed #1127008 (Sergei Glushchenko). Fix for bug #1070856…_view_create_low() in most cases. This significantly improves InnoDB scalability on read-only workloads, especially when the default glibc memory… read_view_open_now() which is another problem originally reported as upstream bug #49169. This also provides much better scalability in InnoDB…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… if there is a transaction that executed a query which opened that table. Bug fixed #1127008 (Sergei Glushchenko). Fix for bug #1070856…_view_create_low() in most cases. This significantly improves InnoDB scalability on read-only workloads, especially when the default glibc memory… read_view_open_now() which is another problem originally reported as upstream bug #49169. This also provides much better scalability in InnoDB…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… results in our tests. In Dimitri’s tests Percona Server scalability is somewhere in between of MySQL 5.5 and MySQL…_io_threads = 8 innodb_io_capacity = 2000 max_connections=5000 table_open_cache=5000 query_cache_type=OFF performance_schema=0 warmup… –num-threads=<1..1024> –test=oltp.lua –oltp_tables_count=8 –oltp-table-size=1000000 –rand-init=on –report-interval=1 –rand…
Post: Opening Tables scalability
November 21, 2006 By 27 Comments
… because of “Opening Tables” stage was taking long. Part of the problem is Innodb is updating stats on each table open which is possibly… he confirmed MySQL has global table cache mutex (LOCK_open) which is held for all open table operation so table opens are serialized. Do not think… blocking physical IO or network operation if you care about scalability. MySQL has same problem with key buffer but that was…
Post: table_cache negative scalability
November 16, 2009 By 23 Comments
… not expect such a table_cache issue – the LRU for cache management is classics and there are scalable algorithms to deal with…. So if you tune table cache is “normal” case and is able to bring down your miss rate (opened_tables) to 10/sec or less by using large table_cache you should do so. However if you have so many tables you…
Post: My "hot" list for next InnoDB features
March 30, 2009 By 18 Comments
…-productive Open InnoDB tables in parallel. Currently opening table is serialized, and it is especially bad at start time, when InnoDB takes probes during opening table, as it is slow operation. See also http://www.mysqlperformanceblog.com/2006/11/21/opening-tables-scalability/. Partially it can…
Comment: Why you don't want to shard.
August 6, 2009 By 34 Comments
…. In MySQL-terms that means at least 1 file per table (.frm), and a lot of pressure on your filesystem to… opening tables scalability in MySQL. See http://www.mysqlperformanceblog.com/2006/11/21/opening-tables-scalability/ and http://www.mysqlperformanceblog.com/2009/06/16/slow-drop-table…
Comment: Opening Tables scalability
March 31, 2009 By 27 Comments
[...] bad at start time, when InnoDB takes probes during opening table, as it is slow operation. See also http://www.mysqlperformanceblog.com/2006/11/21/opening-tables-scalability/. Partially it can be fixed by recent patches by enabling / disabling probes and changing count of [...]
Comment: Opening Tables scalability
November 22, 2006 By 27 Comments
[...] Inspired by PeterZ’s Opening Tables scalability post, I decided to try a little benchmark. This benchmark involved the following: [...]
Post: Is VoltDB really as scalable as they claim?
February 28, 2011 By 3 Comments
… is an in-memory shared-nothing system, and tables are partitioned across multiple servers in the cluster;…J. Gunther’s Universal Scalability Law (USL) to model the cluster’s scalability. If you are not familiar…of benchmarks to satisfy my curiosity. In the opening of this post, I say “should scale” …
