Sponsored Content
Full Discussion: MySQL Performance Problems
The Lounge What is on Your Mind? MySQL Performance Problems Post 303041079 by Neo on Thursday 14th of November 2019 04:08:38 AM
Old 11-14-2019
Update:

To be clear, the main reasons I put the man page table in a different database was to make the main database smaller (75%) smaller; and so the daily backups are faster and use less resources. These backups take up less disk space on both the main server and the backup server.

From a DB CPU perspective, there is little to no performance difference having one huge database or two smaller ones.
 

4 More Discussions You Might Find Interesting

1. AIX

Performance and paging problems

... a disk drive to be 100% busy? hdisk0 100.0 1.3K 342.7 1.3K 22.0 PgspIn 651 % Noncomp 75.5 hdisk1 100.0 1.3K 320.2 1.2K 20.0 PgspOut 6 % Client 75.5 It's really slowing down performance on my system and I would like to know what is causing this. ... (2 Replies)
Discussion started by: bbbngowc
2 Replies

2. SCO

CPU Performance Problems on VMWARE

hi We have migrated SCO 5.0.6 into ESX4, but the VM eats 100% of the virtual CPU. Here is top print from the SCO VM: last pid: 16773; load averages: 1.68, 1.25, 0.98 02:08:41 79 processes: 75 sleeping, 2 running, 1 zombie, 1 onproc CPU states: 0.0% idle, 17.0% user,... (7 Replies)
Discussion started by: ccc
7 Replies

3. AIX

AIX 5.3 performance problems

Hello, I encounter some performance issues on my AIX 5.3 server running in a LPAR on a P520. How do I investigate performance issues in AIX. Is there any kind of procedure that takes me to the steps to investigate my server and find the sub systems that is causing the issues? The performance... (1 Reply)
Discussion started by: petervg
1 Replies

4. Programming

Xlib - Rotation and interpolation of pixmap - Performance problems

I need to rotate a pixmap in XLib with some kind of interpolation to reduce the aliasing. I came up with the following code, which uses bilinear interpolation. It works fine: the rotated image looks perfect, but unfortunately it takes 5 or 6 seconds for each rotation. (in a 300x300, 16 colours... (5 Replies)
Discussion started by: mghis
5 Replies
cleanup_digikamdb(1)													      cleanup_digikamdb(1)

NAME
cleanup_digikamdb - Cleanup the digiKam databases to reduce their sizes and increase access speed SYNOPSIS
cleanup_digikamdb [-t] [-T] [-p] [-h] OPTIONS
-t Include thumbnail databases. -T Only cleanup thumbnail databases. -p path Specify a different database path. If this option is not set or the specified path is invalid, the entry from the configuration file will be used. -h Show command line options. DESCRIPTION
cleanup_digikamdb will cleanup and optimize the digiKam database file. This will, in most cases, lead to a smaller database file size and an increased access speed, because unneeded elements are removed from the database and data is optimized. The program will make sure that no instance of digiKam is running, because it is more safe to have no database access during the optimiza- tion process. It then will read the digiKam configuration file and determine the database location. In a final step the database will be optimized by invoking the sqlite command 'VACUUM;' on it. If more then one database is found in this location, cleanup_digikamdb will op- timize every database found in this path and below. For further explanation, see the following description of the VACUUM command from the sqlite3 website: When an object (table, index, or trigger) is dropped from the database, it leaves behind empty space. This empty space will be reused the next time new information is added to the database. But in the meantime, the database file might be larger than strictly necessary. Also, frequent inserts, updates, and deletes can cause the information in the database to become fragmented - scrattered out all across the data- base file rather than clustered together in one place. The VACUUM command cleans the main database by copying its contents to a temporary database file and reloading the original database file from the copy. This eliminates free pages, aligns table data to be contiguous, and otherwise cleans up the database file structure. AUTHOR
cleanup_digikamdb was written by Andi Clemens <andi dot clemens at googlemail dot com> cleanup_digikamdb 24 October 2011 cleanup_digikamdb(1)
All times are GMT -4. The time now is 09:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy