Tag Info

New answers tagged

0

I suggest to start with a minimal configuration and then make adjustments For mysql 5.6 i suggest: tmp-table-size = 32M max-heap-table-size = 32M read_rnd_buffer_size = 16M join_buffer_size = 16M sort_buffer_size = 1M innodb-flush-method = O_DIRECT innodb-log-files-in-group ...


-1

Your tables do have several indexes to update, did you remember to run a optimize table from time to time? /usr/bin/mysqlcheck -o --auto-repair MyDatabaseName This will optimize all tables and indexes in the Database MyDatabaseName. Depending on how your data looks this might help with INSERT and SELECT speed. I guess since you have tried everything you ...


4

but using the "limit" keyword cant prevent the search over the whole set of data(is it correct?) Correct; it'll just limit how many results are returned. For some kinds of query it can also limit how many are scanned in the first place, but you can't rely on that in the general case. does PostgreSQL database have to create this 1M search result ...


0

There is no way, there is only the journey! You could start here with MySQLTuner - it's a tuning script which issues recommendations - it doesn't modify anything on the server and I have read (can't find ref, sorry) that it's impact on performance while running is minimal. There's also this - but it seems to be dead. I'll just repeat the warning that comes ...


0

Except for the general log and the slow log with very small long_query_time, performance shouldn't get affected too much when on, as most logging should be written to the filesystem cache (those logs do not need to be transactional safe). There are certain combination of configuration and workloads that certainly can affect negatively performance: ...



Top 50 recent answers are included