Re: internal storage
On 20 Sep 2004, at 5:54, Jim Hendricks wrote:
>
>
> posted by: Jim Hendricks <jim at bizcomputinginc.com>
>
> Michael Raley wrote:
> >
> >
> > Jim Hendricks wrote:
> > <snip>
> > > My question is are string sequences then stored as 4 byte atoms or as
> > > 1 byte atoms?
> > <snip>
> > Yes, string sequences as stated are really just numeric sequences.
> > {65,66,67,3265} is internally the same as "ABC" & 3265
> > You can sorta obscure plain text passwords in source files by writting
> > them in sequence format
> >
> > i.e. pwd = {325,330,335}/5
> >
> > There are two workarounds that I tried because I had to split 24 megabyte
> > revenue usage reports apart, creating a new subreport for each revenue
> > department key found in the page headers. This would run very slow on the
> > old
> > win 95 machines it had to be run on, constantly chugging through virtual
> > memory.
Did you try faster hardware under the win95? I recently spent an hr optomising
at a
function, and trimmed over an hour of runtime out of it (went from 20 minutes to
under
a second, using indexes extensively and NOT resizing the sequences).
> > The first was to try to internally pack three atoms into one integer
> > (the library is in the archives)
> > so incompress({65,66,67}) would return {656667}
> Yes, that was suggested by someone else, but if I were to go with all the
> work of packing/unpacking I would stuff 4 chars per atom unless there's some
> limitation on use of all 32 bits of an integer atom.
Several people have written assorted memory storage files for your task. Derek
wrote
one, Euman wrote at least one this year, Allen Robnett did something, Jordah did
something along these lines, and i wouldn't be surprised if Jiri did too. Try
Euman's
for speed, or Derek's for versatility,, or Jordah's. Euman's uses a windoze C
call to do
fast pattern searches in the memory block. It's plenty easy to drop blocks of
the raw
memory into a sequence to do Eu operations on them.
Kat
|
Not Categorized, Please Help
|
|
