On Tue, 04 Oct 2011 13:53:29 +0100, James wrote in message <04ab1637-d3b3-4396-9a68-4910e1235...@mac.com>:
> > On 4 Oct 2011, at 13:34, Curtis Olson wrote: > > > Here's a random idea on the writer side: > > > > Would it be possible to do something like: > > > > if (size of any of my structures are > 65535) then > > write_32bit_index_btg() > > else > > write_16bit_index_btg() > > endif > > > > Then we'd be spending are larger index bits on the files that need > > them, but not paying the penalty across the board on every scenery > > file. > > Entirely possible, yes - however I *suspect* it's unnecessary since > gzip will compress the larger indices back down to a few % larger > than what we currently have. ..how about write_64bit_index_btg(), could it index all tile files? > Of course, I can't confirm or deny that suspicion until I upgrade the > writer code path too :) > > James -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
