You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already tested with mixed Kontalk 2.x and 3.x servers on the same host that concurrent accesses to the same keyring causes crashes, so using multiple contexts on the same keyring won't work.
Also, when keyrings get big (as in very big), GnuPG performance degrades like hell.
Crazy thing to make concurrent calls to GnuPG
Waiting to implement an efficient GnuPG library implementation...
Since GnuPG is currently used as a key/value storage (where keys are fingerprints), the key space can be splitted (e.g. 16 GnuPG home directories for each first hex digit of the fingerprint; for what is worth, every even number from 2 to 16 will do).
By using multiple keyrings, fingerprint key space can be splitted in many parts and GnuPG operations can happen on multiple contexts simultaneously.
configuration parameter for number of partitions
splitted keyring implementation, transparent to the caller (make an interface to the standard gnupg-for-java methods)
shell script for converting unified keyring to splitted keyring
The text was updated successfully, but these errors were encountered:
I already tested with mixed Kontalk 2.x and 3.x servers on the same host that concurrent accesses to the same keyring causes crashes, so using multiple contexts on the same keyring won't work.
Also, when keyrings get big (as in very big), GnuPG performance degrades like hell.
Crazy thing to make concurrent calls to GnuPG
Since GnuPG is currently used as a key/value storage (where keys are fingerprints), the key space can be splitted (e.g. 16 GnuPG home directories for each first hex digit of the fingerprint; for what is worth, every even number from 2 to 16 will do).
By using multiple keyrings, fingerprint key space can be splitted in many parts and GnuPG operations can happen on multiple contexts simultaneously.
The text was updated successfully, but these errors were encountered: