lihao has asked for the wisdom of the Perl Monks concerning the following question:
Hi, folks:
I am maintaining a long list of 20M records, the unique key in this table contains multiple fields and now I need to setup an ID (not sequential numbers, need randomness) for each of these unique records. Currently I am using a sub-string of hexadecimal generated by SHA1 method. This is OK except that the length of ID is too long in order to keep the uniqueness. Is there a way/method in Perl that I can transfer the 20-byte hexadecimal into a shorter string contains [0-9a-z](case insensitive)?
many thanks..
lihao
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Question: methods to transfer a long hexadicimal into shorter string
by FloydATC (Deacon) on Aug 07, 2009 at 16:43 UTC | |
Is there any reason why you need human-readable unique keys? Why not pack the key as a binary string using pack() while you're at it?
--
Time flies when you don't know what you're doing
| [reply] |
|
Re: Question: methods to transfer a long hexadicimal into shorter string
by Marshall (Canon) on Aug 07, 2009 at 17:48 UTC | |
You haven't explained how big this DB is? I guess that it is possible although VERY unlikely that this DB is small enough to be memory resident. If we just think about storing just the 20M SHA-1 signatures, each is 20 bytes. For the hardware, powers of 2 are magic and it goes: 2,4,8,16,32. In a practical sense, each signature will take 32 bytes: 8 32 bit(4 byte) words or 16 16 bit(2 byte) words. That is a fair amount of memory for 20M records (like 640MB) and these "keys", (they are SHA-1 signatures) aren't even unique! I don't know what your plan is to deal with that. Oh, of course besides the memory to store the SHA-1 signatures, there has to be some data that points to something (on disk or wherever). That will take some bytes too! You need a Database. Perl DBI in its many flavors can easily handle 20M records. Forget SHA-1 or SHA-2 that makes no sense. Let the DB use its hash algorithm. | [reply] |
by lihao (Monk) on Aug 07, 2009 at 21:16 UTC | |
Thank everyone for the reply Let me explain more about my project. I have 20M email listing (saved in MySQL) which we want to track in our campaigns. So instead of using original emails on the related URLs, we want to use IDs. 20-byte hexadecimal is good enough for uniqueness of 20M emails. While I am trying to find better options, i.e., if we can use shorter ID, we can significantly reduce the table size and there are more benefit from doing so... For testing purpose, I used 3M emails and 8-byte ID and Digest::SHA1 and Convert::zBase32 to build the IDs
I was hoping the second one could at least give me better uniqueness. but the result is: I got 773 duplicated IDs from setid_1 and 676131 duplicated IDs from setid_2. Any better way to handle such issue? thanks again lihao | [reply] [d/l] |
by Marshall (Canon) on Aug 07, 2009 at 23:34 UTC | |
If you use all 32 bits, you get 2x as much. Obviously you can have the DB generate those numbers.
It sounds like what you want to is encode some long string
into something a LOT shorter representation that doesn't have to be unique. There are all sorts of hash functions, but since we are programming in Perl, my initial thought would be: how does Perl do this? This is the Perl hash function written in C:
Internally Perl chops down the number of bits to get a practical index number by: index= hash & xhv_max. In your case, forget it - don't worry about what xhv_max is, use all the bits! (well maybe you should consider implications of the sign bit) If 32 bits isn't enough, then 64 bits is gonna do it, that's 8 bytes. Don't mess with 48 bits or something like that. Powers of 2 are magic on most machines commonly in use, eg: 2,4,8,16,32,64,128. In summary, forget about SHA-1 or SHA-2 or any other form of encryption, use an efficient hash encoding technique. I would try a 32 or 64 bit version of what Perl itself does! Update:The Perl hash algorithm works very well based upon my subjective empirical judgment with just 120K hash key structures. Anyway, I am confident that 20 bytes aren't necessary and that 8 bytes will yield the "uniqueness" that you need. That would allow the keys to be resident in memory. But, I think that the idea of using a DB is even better as it scales gracefully to HUGE structures. | [reply] [d/l] [select] |
|
Re: Question: methods to transfer a long hexadicimal into shorter string
by BrowserUk (Patriarch) on Aug 07, 2009 at 21:12 UTC | |
I need to setup an ID (not sequential numbers, need randomness) for each of these unique records. Why not have the DB give you the randomness you need? If you give each record a sequential (autoincrement) record number--which guarentees uniqueness--and then have an auxillary table which maps that recno to a random 'tag' of say 6 characters: A-Z. That would give you 300 million unique 6-char tags which should be sufficient to be going on with. And with a properly indexed table, the lookup should be very quick with any DB worth its disk space. If you ever need to expand further you can add a-z to double that; or move to seven chars which would cater for 8 billion. The toughest part of this suggestion is generating the recno/tag mapping. Or rather, shuffling the tags once you've generated them which Perl makes easy. Shuffling a 300e6 element array is a memory intensive process even if you use an in-place shuffle. A possible solution to this is to break the problem into 2 parts. Shuffling two small sets of 3-char stems & suffixes is trivial, and combining them at output time means you require minimal memory (~16MB), and it is very fast. It takes about a minute to produce 20e6 or roughly an hour if you wanted the full 300e6:
Whilst not truly random--there are some possible sequences that cannot be generated--it is sufficiently random (ie. unguessable) for many purposes. If you needed to move to 8 billion/7-char tags, using a 4-3 or 5-2 split works equally well. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] [d/l] |
|
Re: Question: methods to transfer a long hexadicimal into shorter string
by QM (Parson) on Aug 07, 2009 at 17:16 UTC | |
-QM | [reply] [d/l] [select] |