in reply to Re: Serializing a large object
in thread Serializing a large object

I am currently using nstore with a fd opened using gzip IO layer. Other solutions will be most welcomed. What exactly would you like me to supply and where should I put it?

Replies are listed 'Best First'.
Re^3: Serializing a large object
by BrowserUk (Patriarch) on Oct 09, 2010 at 13:53 UTC

    A small set (say 1000 or so) "typical" input ranges; and a hundred or so test ranges along with the result counts when compared against the supplied input set. Timings of how long it took to run would also be useful.

    As for how to exchange them, email seems possible. One set of 1000 pairs; plus 1 set of 100 hundred pairs + counts; plus a time won't take much space. You could probably even post them here. /msg me for a email address if you want to go that route.

    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]
      coordinates are in 1 .. 877879 (both inclusive). I used some real data so the number of ranges is 2777 and it followed by some 1000 queries and their results.
      Read more... (67 kB)

[reply]
[d/l]
[select]

        Thanks. How long did that take using your current solution? A load time and size fr compressed nstore data; and the time taken to perform the search and produce the results would be useful.

        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]

In Section Seekers of Perl Wisdom