I'm using MySQL in a asp.NET project I'm currently working on, I performed tests MySQL .NET provider did some tests to do but unfortunately I'm not very pleased with the result.
A very simple loop which only opens the connection is 10x faster in SQL Server:
// MySQL const string CONNECTION_STRING = "server = Sthaniyhost; database = Testdb; user id = root; password = mypassword; maximum pool size = 250; "; (Int i = 0; i & lt; 5000; i ++ ((MySqlConnection con = new MySqlConnection (CONNECTION_STRING)) for) {con.Open ();}} // SQL Server Const string CONNECTION_STRING = "Data Source = Localhost; initial catalog = testdb; integrated security = true; maximum pool size = 250; "; (int i = 0; i SQL server everything too fast (select, update, insert, etc ..) am I wrong? is there any server variables Change me More info:
- I run MySQL on Windows (5.0.51A Community-NT)
- Testing using SQL Server 2005
- specs: Windows XP SP2, the CPU Intel 1.6 GHz dual core 1024 MB RAM
configuration of this Meskaluleshn:
< code> [client] port = 3306 socket = /tmp/miclksok [Micld] port = 3306 socket = /tmp/miclksok skip-locking Ke_bfr = 384M Max_alloved_packet = 1M Table_kas = 512 Sort_bfr_saij = 2M Read_bfr_saij = 2M Read_rat_bfr_saij = 8m my_sort_buffer_size = 64m thread_cache_size = 8 query_cache_size = 32m thread_concurrency = 8 server-id = 1 [my Sqldump] Quick max_allowed_packet = 16M [mysql] no-auto-reshash [ISM] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2m write_buffer = 2m [mysmak] key_buffer = 256m sort_buffer_size = 256m read_buffer = 2m writing_buffer = 2m [MySQLPCopy] Interactive Timeout
Thanks any suggestions ...
< P> SQL Server uses connection pooling by default: When each connection is closed with the exact same connection The string is returned to the pool. Backing the connection back to the pool is more efficient than making connections from scratch. I think mySQL connection pooling by default
does not provide 
Comments
Post a Comment