The other comments address well that md5 is a hashing function which is
implicitly non-reversible. It's also not a very secure hashing algorithm
as it's vulnerable to both collision attacks and length extension
attacks (more reading here for interest...
I have tried the Immediate garbage collection mode in my application but
didn't get much speed up. Can I clarify what metric you're using when
you say you didn't get much speed up. Just to restate, when you use
immediate garbage collection you no lon...
Ah yes you're right, multiple entries of qty/price for a given uid/tid
will create nested columns in the by clause response. Agreed, memory
fragmentation definitely not the issue here, just providing
documentation supporting that claim
Hi there, Firstly, what you're seeing here isn't memory fragmentation
due to nested columns. Looking at the documentation the memory
fragmentation issue in relation to garbage collection is when KDB/Q
can't find contiguous blocks of memory to release...
Hi DG, Here are a few solutions depending on requirements/specifics: 1.
Depending on how dynamic the queries are, i.e. if it's a mostly fixed
list of aggregations, I would suggest using a Real Time Subscriber (RTS)
and creating tables for the differe...