We are developing a application using wordpress as its base.Application development is almost done and its time to go into production.Now we are doing the performance improvements in server side

Here is our application deployment architecture

Server1 (CentOS7): Nginx and php-fpm
Server2 (Percona MySQL 5.6)

Our issue is when we run mysqltuner.pl script in mysql server i am getting Temporary tables created on disk: 69% (7K on disk / 10K total)

I think the temporary table created on HDD space reduced the application performance. How to avoid to creating it into HDD instead of its memory?

Hello

http://dev.mysql.com/doc/refman/5.6/...ary-files.html

Are you sure it really is a problem?

You have 7k used. Mysql will always use temp files for some operations. For example "ALTER TABLE ..." will usually use it. If it does use the disk a lot, it can help to raise the size of some buffer. But you will have to investigate what the problem really is.

Or you could simply setup a ramdisk for /tmp with tmpfs.

https://wiki.centos.org/TipsAndTricks/TmpOnTmpfs

How big is your database? And how much memory do you have? Transaction rate? Mostly readers or mostly writers?

Thanks for your reply.
Our database server is a 2GB CentOS system. and here is the my.cnf values

# CACHES AND LIMITS #
tmp-table-size = 256M
max-heap-table-size = 512M
query-cache-type = 1
query-cache-size = 16M
max-connections = 500
thread-cache-size = 50
open-files-limit = 65535
table-definition-cache = 4096
table-open-cache = 512

# INNODB #
innodb-flush-method = O_DIRECT
innodb-log-files-in-group = 2
innodb-log-file-size = 128M
innodb-flush-log-at-trx-commit = 1
innodb-file-per-table = 1
innodb-buffer-pool-size = 768M
innodb_buffer_pool_instances = 1
innodb_sort_buffer_size = 2M

@Guttorm's suggestions are right on and are in line with the DBA's (me) perspective. Without an idea of how the database is being used and the projected transaction count, it would be hard to tune MySQL's performance. When you say a 2GB Centos system, what do you mean? 2GB of RAM? If your application is of the LAMP variety and you need performance, having the temp area on a spindle might not be the first issue to address because there will be more to tune outside of running from a disk. Is your machine dedicated to running the database or does it also run the application?

My apologies, totally glazed over the architecture bit from above.