Hello Jim,
Tuesday, May 11, 2010, 8:36:46 PM, you wrote:
JF> On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
>> On Sun, May 9, 2010 at 8:33 PM, Jim Fulton wrote:
>>>
>>> Our recent discussion of compression made me curious so I did some
>>> analysis of pickle sizes in one of our large data
On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
> On Sun, May 9, 2010 at 8:33 PM, Jim Fulton wrote:
>>
>> Our recent discussion of compression made me curious so I did some
>> analysis of pickle sizes in one of our large databases. This is for a
>> content management system. The database is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam GROSZER wrote:
> Hello Jim,
>
>
>
> Tuesday, May 11, 2010, 4:46:46 PM, you wrote:
>
> JF> On Tue, May 11, 2010 at 7:47 AM, Adam GROSZER wrote:
>>> Hello Jim,
>>>
>>> Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
>>>
>>> JF> On Tue, May 11, 20
Hello Jim,
Tuesday, May 11, 2010, 4:46:46 PM, you wrote:
JF> On Tue, May 11, 2010 at 7:47 AM, Adam GROSZER wrote:
>> Hello Jim,
>>
>> Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
>>
>> JF> On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER wrote:
Hello Jim,
Tuesday, May 11, 2010, 1
On Tue, May 11, 2010 at 7:47 AM, Adam GROSZER wrote:
> Hello Jim,
>
> Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
>
> JF> On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER wrote:
>>> Hello Jim,
>>>
>>> Tuesday, May 11, 2010, 12:33:04 PM, you wrote:
>>>
>>> JF> On Tue, May 11, 2010 at 3:16 AM, Adam
On May 11, 2010, at 9:53 AM, Lennart Regebro wrote:
> On Tue, May 11, 2010 at 14:47, Adam GROSZER wrote:
>> Probably that crappy data would make the unpickler fail... or wait a
>> second... the unpickler is a **SECURITY HOLE** in python, isn't it?
>> That means feed it some random data... and st
On Tue, May 11, 2010 at 14:47, Adam GROSZER wrote:
> Probably that crappy data would make the unpickler fail... or wait a
> second... the unpickler is a **SECURITY HOLE** in python, isn't it?
> That means feed it some random data... and stay tuned for the
> unexpected.
That a bitflip would genera
Hello,
Tuesday, May 11, 2010, 1:59:17 PM, you wrote:
N> Am 11.05.2010, 13:47 Uhr, schrieb Adam GROSZER :
>> Hello Jim,
>>
>> Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
>>
>> JF> On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER
>> wrote:
Hello Jim,
Tuesday, May 11, 2010, 12:33:0
Am 11.05.2010, 13:47 Uhr, schrieb Adam GROSZER :
> Hello Jim,
>
> Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
>
> JF> On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER
> wrote:
>>> Hello Jim,
>>>
>>> Tuesday, May 11, 2010, 12:33:04 PM, you wrote:
>>>
>>> JF> On Tue, May 11, 2010 at 3:16 AM, Adam
Hello Jim,
Tuesday, May 11, 2010, 1:37:19 PM, you wrote:
JF> On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER wrote:
>> Hello Jim,
>>
>> Tuesday, May 11, 2010, 12:33:04 PM, you wrote:
>>
>> JF> On Tue, May 11, 2010 at 3:16 AM, Adam GROSZER wrote:
Hello Jim,
Monday, May 10, 2010, 1:2
On Tue, May 11, 2010 at 7:13 AM, Adam GROSZER wrote:
> Hello Jim,
>
> Tuesday, May 11, 2010, 12:33:04 PM, you wrote:
>
> JF> On Tue, May 11, 2010 at 3:16 AM, Adam GROSZER wrote:
>>> Hello Jim,
>>>
>>> Monday, May 10, 2010, 1:27:00 PM, you wrote:
>>>
>>> JF> On Sun, May 9, 2010 at 4:59 PM, Roel Br
Hello Jim,
Tuesday, May 11, 2010, 12:33:04 PM, you wrote:
JF> On Tue, May 11, 2010 at 3:16 AM, Adam GROSZER wrote:
>> Hello Jim,
>>
>> Monday, May 10, 2010, 1:27:00 PM, you wrote:
>>
>> JF> On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
That's really interesting! Did you notice any i
On Tue, May 11, 2010 at 3:16 AM, Adam GROSZER wrote:
> Hello Jim,
>
> Monday, May 10, 2010, 1:27:00 PM, you wrote:
>
> JF> On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
>>> That's really interesting! Did you notice any issues performance wise, or
>>> didn't you check that yet?
>
> JF> I di
Hello Jim,
Monday, May 10, 2010, 1:27:00 PM, you wrote:
JF> On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
>> That's really interesting! Did you notice any issues performance wise, or
>> didn't you check that yet?
JF> I didn't check performance. I just iterated over a file storage file,
J
On Sun, May 9, 2010 at 4:59 PM, Roel Bruggink wrote:
> That's really interesting! Did you notice any issues performance wise, or
> didn't you check that yet?
I didn't check performance. I just iterated over a file storage file,
checking compressed and uncompressed pickle sizes.
Jim
--
Jim Fult
On Sun, May 9, 2010 at 8:33 PM, Jim Fulton wrote:
> Our recent discussion of compression made me curious so I did some
> analysis of pickle sizes in one of our large databases. This is for a
> content management system. The database is packed weekly. It doesn't
> include media, which are in blo
16 matches
Mail list logo