db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <david.vancouver...@gmail.com>
Subject Re: Database storage overhead
Date Fri, 05 Feb 2010 20:10:58 GMT
Yep, definitely can do that, thanks.  I was just wondering if you had some
heuristics I could use.

On Fri, Feb 5, 2010 at 11:30 AM, Bryan Pendleton
<bpendleton@amberpoint.com>wrote:

> But that's assuming a "perfect" layout for the database.  I am wondering,
>> how much overhead should I account for?
>>
>
> My feeling is: try it and see. It shouldn't take longer than a
> few hours to construct a test program which manufactures semi-random
> data along the profile that you anticipate. Then just generate that
> data, store it into the db, and see how big it turns out to be.
>
> You surely don't need all 1 million rows; a few thousand rows is
> probably plenty to allow you to observe the overheads and extrapolate.
>
> thanks,
>
> bryan
>
>


-- 
David W. Van Couvering

http://www.linkedin.com/in/davidvc
http://davidvancouvering.blogspot.com
http://twitter.com/dcouvering

Mime
View raw message