![]() ![]() When this happens, the time to retrieve a certain info from the database increases (sometimes a lot) because of 1) disk fragmentation - the disk head will need to jump from sector to sector to find the requested info and 2) pointer / page fragmentation: the program needs to jump from page to page in the disk cache maintained in memory (because of a -very- deep chain of pointers traversed frequently) in order to locate and retrieve the desired record / index bucket. Keep the above terms in mind when you read the descriptions below.īecause of the way the operating system maintains disk storage, over time the MP database files can become fragmented into several pieces stored in different locations on the drive. So, Cataloged = Scanned + User Entered Information A Cataloged file is a Scanned file for which an user has added information (information = data with human meaning): color, rating, keywords/categories, tags/albums, user comments (& other human generated IPTC), etc.A Scanned file is the a file which is added to (entered into) the database by the (automatic) subsystem which builds the thumbnails and enters all the basic (meta)data about the said file: name, directory, EXIF, machine-generated IPTC etc.The options there are explained below.įirst, however, it is important to understand the notion of cataloged vs scanned In the main menu, go to Tools | Settings | Database and press the Optimize. Periodically optimize your Database: See the next section for how to do this.If you have a big image collection and lots of RAM memory, set the value at 100 - 200 MB or even more. Increase the "Memory usage for database engine" settings value (in the Tools | Settings | Database panel).You can change the paths from the 'Other settings' pane. Note> To change the location of your databases, navigate to Tools | Settings | Integration | Paths.If you can, have the two databases themselves (xnview.db and thumbs.db) each on separate drives - this will speedup access.Try to put the databases on a secondary (non-busy) drive (not the drive with the operating system on it). ![]() Keep your databases - especially the Thumbs.db database - on SSDs rather than Hard Disks.square).Īssure the best storage environment for your databases width ratio proportional to the shape of the thumb images you want (vertical vs. 10% or so) by adjusting the values in the Setup dialog, but keep the height vs. Next, reduce the resulting thumb dimensions a small amount (e.g. The dialog will capture the thumb size you formerly selected using the slider in the Browser. Then, go to Tools | Settings | Database and press Get thumbnail Size. Use the thumbs slider (in the Browser) to approximate the (normal) thumb size that works best for you, day-to-day. As a matter of policy, be willing to accept a slight 'fuzziness' in the appearance of your thumbnails. XnView MP can dynamically (and temporarily) resize the thumbs to fit which ever thumb size you select using the browser thumbnail sizer, but without changing the stored size. ![]() reducing the amount of Input/Output Operations from/to database/disk, dramatically improving the speed.īe conservative with the size of the stored thumbnails. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |