Menu

#16 slow importing of full keyrings

open
cks_import (9)
3
2005-04-28
2004-07-26
No

The import from scratch of a full keyring dump in the
database is very slow.

In the same machine (2xPIII-800, 1Gb RAM, SCSI RAID 5)
the import of a full dump (split of 2Mb PGP keys) last
3 days . The import of the database in a pksd server
last less than 1 day.

The problems seems to be related to the indexes
perhaps cks_import should drop the index on the
database before importing the rings and
later create again the index when the upgrade is completed.

Discussion

  • V. Alex Brennen

    V. Alex Brennen - 2005-04-28
    • priority: 5 --> 3
    • assigned_to: nobody --> vab
     
  • V. Alex Brennen

    V. Alex Brennen - 2005-05-07

    Logged In: YES
    user_id=52593

    This is a complex issue. I plan to support *dbm style
    databases which will dramitally improve the import speed.
    However, the real issue is that CKS does more parsing I
    believe than pksd when parsing packets, so more CPU time is
    used. I'm not sure I want to remove this code as it helps
    keep invalid or damaged keys from being imported.

    A rewrite of the code to use a buffered stream fromat import
    may help, but I am going to put such work aside until the
    server becomes stable and reaches v1.0.0. I may be able to
    use mmap to speed thing up with the current code.

     

Log in to post a comment.

MongoDB Logo MongoDB