Re: Shared game-data
From: Jay Dee <ais01479_at_aeneas.net>
Date: Mon, 01 May 2006 01:42:18 GMT
Message-ID: <_Hd5g.18055$YI5.2066_at_tornado.ohiordc.rr.com>
>> Neo wrote:
>>
>>>>> Normalization is a technique which among other things, reduces
>>>>> performance.
>>>>
>>>>
>>>> That's a teaser. What are the other things?
>>>> And, please, just what performance is reduced?
>>>
>>>
>>> That statement should have been more like: In general, normalization is
>>> a very important technique that allows efficient data mgmt; however,
>>> the time it takes to normalize data and retreive normalized data
>>> (relatively small amounts of data) reduces performance and as such may
>>> not be appropriate in apps where maximum performance is required.
>>
>>
>> Lots of questions:
>>
>> "efficient data mgmt" What is data mgmt and how does one measure its
>> efficiency?
>>
>> "time it takes to normalize data" What time? When is it spent?
>>
>> "time it takes to... retrieve normalized data" This is slower than...
>> what?
>>
>> "maximum performance" Do you mean minimum time?
>>
>>> For example, in dbd, where performance is not a primary requirement and
>>> data mgmt is, all represented things are auto-normalized (no redundant
>>> representations).
>>
>>
>> Could you explain a bit more of this "dbd" and the differences between
>> performance and data mgmt? And I'd be interested in hearing more about
>> how "things are auto-normalized."
Date: Mon, 01 May 2006 01:42:18 GMT
Message-ID: <_Hd5g.18055$YI5.2066_at_tornado.ohiordc.rr.com>
[Quoted] Bob Badour wrote:
> Jay Dee wrote: >
>> Neo wrote:
>>
>>>>> Normalization is a technique which among other things, reduces
>>>>> performance.
>>>>
>>>>
>>>> That's a teaser. What are the other things?
>>>> And, please, just what performance is reduced?
>>>
>>>
>>> That statement should have been more like: In general, normalization is
>>> a very important technique that allows efficient data mgmt; however,
>>> the time it takes to normalize data and retreive normalized data
>>> (relatively small amounts of data) reduces performance and as such may
>>> not be appropriate in apps where maximum performance is required.
>>
>>
>> Lots of questions:
>>
>> "efficient data mgmt" What is data mgmt and how does one measure its
>> efficiency?
>>
>> "time it takes to normalize data" What time? When is it spent?
>>
>> "time it takes to... retrieve normalized data" This is slower than...
>> what?
>>
>> "maximum performance" Do you mean minimum time?
>>
>>> For example, in dbd, where performance is not a primary requirement and
>>> data mgmt is, all represented things are auto-normalized (no redundant
>>> representations).
>>
>>
>> Could you explain a bit more of this "dbd" and the differences between
>> performance and data mgmt? And I'd be interested in hearing more about
>> how "things are auto-normalized."
> > > Please stop encouraging the shameless ignorant and spare us all.
Okay, I'm done.
(For some reason the phrase "box of rocks" keeps popping into my thoughts.) Received on Mon May 01 2006 - 03:42:18 CEST