Cookies are short reports that are sent and stored on the hard drive of the user's computer through your browser when it connects to a web. Cookies can be used to collect and store user data while connected to provide you the requested services and sometimes tend not to keep. Cookies can be themselves or others.
There are several types of cookies:
Technical cookies that facilitate user navigation and use of the various options or services offered by the web as identify the session, allow access to certain areas, facilitate orders, purchases, filling out forms, registration, security, facilitating functionalities (videos, social networks, etc..).
Customization cookies that allow users to access services according to their preferences (language, browser, configuration, etc..).
Analytical cookies which allow anonymous analysis of the behavior of web users and allow to measure user activity and develop navigation profiles in order to improve the websites.
So when you access our website, in compliance with Article 22 of Law 34/2002 of the Information Society Services, in the analytical cookies treatment, we have requested your consent to their use. All of this is to improve our services. We use Google Analytics to collect anonymous statistical information such as the number of visitors to our site. Cookies added by Google Analytics are governed by the privacy policies of Google Analytics. If you want you can disable cookies from Google Analytics.
However, please note that you can enable or disable cookies by following the instructions of your browser.
Digging into mySQL settings can be time consuming, like with any other component. Most of the time, and just by changing a few settings, you can expect a performance increase. The problem is to change what, and to which value. This is where tuning-primer.sh help you:
SLOW QUERIES Current long_query_time = 5 sec. You have 2856 out of 4725688 that take longer than 5 sec. to complete The slow query log is enabled. Your long_query_time seems to be fine WORKER THREADS Current thread_cache_size = 128 Current threads_cached = 55 Current threads_per_sec = 0 Historic threads_per_sec = 0 Your thread_cache_size is fine MAX CONNECTIONS Current max_connections = 100 Current threads_connected = 15 Historic max_used_connections = 55 The number of used connections is 55% of the configured maximum. Your max_connections variable seems to be fine.
MEMORY USAGE Max Memory Ever Allocated : 305 M Configured Max Per-thread Buffers : 1017 M Configured Max Global Buffers : 143 M Configured Max Memory Limit : 1 G Total System Memory : 2.99 G Max memory limit seem to be within acceptable norms
KEY BUFFER Current MyISAM index space = 4 M Current key_buffer_size = 5 M Key cache miss rate is 1 : 3740 Key buffer fill ratio = 35.00 % Your key_buffer_size seems to be too high. Perhaps you can use these resources elsewhere
QUERY CACHE Query cache is enabled Current query_cache_size = 128 M Current query_cache_used = 27 M Current query_cach_limit = 2 M Current Query cache fill ratio = 21.13 % Your query_cache_size seems to be too high. Perhaps you can use these resources elsewhere MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS Current sort_buffer_size = 4 M Current record/read_rnd_buffer_size = 1020 K Sort buffer seems to be fine
JOINS Current join_buffer_size = 1.00 M You have had 7065 queries where a join could not use an index properly You should enable "log-queries-not-using-indexes" Then look for non indexed joins in the slow query log. If you are unable to optimize your queries you may want to increase your join_buffer_size to accommodate larger joins in one pass.
Note! This script will still suggest raising the join_buffer_size when ANY joins not using indexes are found.
Here is the easiest way to run a daily backup of your database using linux crontab. Thanks to our everyday increasing mailbox size (Thanks Gmail) and their nature to be quite safe for saving document, let’s use them to store the full backup of all our Mysql database! Requirements Having a shell access to your linux box Creating a user with limited mysql rights: SELECT and LOCK_TABLES is enough, For example a user backup_user with a password ChhdeqyqUzd75687fOnmYar Installing Mpack: …
In this small post, I’ll show you how to reset the MySQL password in case you lost it. You’ll need at least the root access of the machine where MySQL run. Reset the MySQL root password Resetting the root password of a MySQL database in case you lost it, is really easy. # /etc/init.d/mysql stop Now start the database in the background, via the mysqld_safe command. Start MySQL with a flag to tell it to ignore any username/password restrictions which …
I found this interesting tool (beside tuning-primer.sh) while trying to optimizing my server setting for Joomla! mysqlreport mysqlreport makes an easy-to-read report of important MySQL status values. Unlike SHOW STATUS which simply dumps over 100 values to screen in one long list, mysqlreport interprets, formats, and then nicely presents the values in report readable by humans. Numerous example reports are available at the mysqlreport web page. The benefit of mysqlreport is that it allows you to very quickly see a …
According to this MySQL page here, you can win 30 to 50% more performances using MySQL jdbc named pipe! Named pipes only work when connecting to a MySQL server on the same physical machine as the one the JDBC driver is being used on. In simple performance tests, it appears that named pipe access is between 30%-50% faster than the standard TCP/IP access. As default, when you install mySQL on windows using the installer, TCP IP is the default option. …
One of the most important rule is to always backup your data with multiple tools on different medium, just in case of. Just imagine 5 minutes that you lose everything, what you have done in the last 3 months on your homepage..ok still not crying? you loose hundred of hours of work, nightly debugging, customizations, hours of Gimp/Photoshop, lengthy and good written articles... With Joomla! and now with nearly all CMS, the most important thing to backup is the database. …
I publish here some of my server settings in the hope that it will also help others... Server Setup AMD64 1 Gb RAM, Linux OSS 10.0, 7 Joomla instances (one being waltercedric.com with 250'000 unique visitors per months), 1 simple machine forums, 3 gallery2 install All MySQL tables are myISAM (table locking instead of row loacking in innodb, myIsam make sense as ther is more read then insert) # vi in /etc/my.cnf Below the diff command between a standard MySQL …