You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by "Delapasse, Deanna" <dd...@oceaneering.com> on 2015/05/20 00:10:19 UTC
dbname.data is huge
Sorry for all these emails! One more really easy question and I promise to
stop bothering y'all for a while.
While running locally on my laptop using the simple example my dbname.data
file (I guess this is my hsqldb) get huge!!! I'm only indexing 30 rows
over and over (working on some connector enhancements and learning Elastic
Search), but my dbname.data is already > 11GB.
I don't need to keep any of this data. Is there a fast, easy way to just
'reset' my db? I don't mind recreating my output/repo/jobs?
I'm in a meeting right now listening to my boss tell some bigwigs how we're
got this all figured out (which explains all my stress-filled emails) :-).
Thanks!!!
Deanna
Re: dbname.data is huge
Posted by Karl Wright <da...@gmail.com>.
FWIW, if you want to "reset", just delete the hsqldb database files and
start over. This happens when you "ant clean" as well.
Karl
On Tue, May 19, 2015 at 9:34 PM, Karl Wright <da...@gmail.com> wrote:
> Hi Deanna,
>
> HSQLDB is not great for production use for a number of reasons; it's also
> unconstrained in memory consumption.
>
> Indexing 30 rows over and over should not create a huge table; I suspect
> that if you queried it you would find the number of rows to be tiny. The
> reason it gets big has to do mainly with HSQLDB disk management algorithms
> not being that great. So try MySQL or PostgreSQL is my suggestion.
>
> Karl
>
>
> On Tue, May 19, 2015 at 6:10 PM, Delapasse, Deanna <
> ddelapasse@oceaneering.com> wrote:
>
>> Sorry for all these emails! One more really easy question and I promise
>> to stop bothering y'all for a while.
>>
>> While running locally on my laptop using the simple example my
>> dbname.data file (I guess this is my hsqldb) get huge!!! I'm only indexing
>> 30 rows over and over (working on some connector enhancements and learning
>> Elastic Search), but my dbname.data is already > 11GB.
>>
>> I don't need to keep any of this data. Is there a fast, easy way to just
>> 'reset' my db? I don't mind recreating my output/repo/jobs?
>>
>> I'm in a meeting right now listening to my boss tell some bigwigs how
>> we're got this all figured out (which explains all my stress-filled emails)
>> :-).
>>
>> Thanks!!!
>> Deanna
>>
>
>
Re: dbname.data is huge
Posted by Karl Wright <da...@gmail.com>.
Hi Deanna,
HSQLDB is not great for production use for a number of reasons; it's also
unconstrained in memory consumption.
Indexing 30 rows over and over should not create a huge table; I suspect
that if you queried it you would find the number of rows to be tiny. The
reason it gets big has to do mainly with HSQLDB disk management algorithms
not being that great. So try MySQL or PostgreSQL is my suggestion.
Karl
On Tue, May 19, 2015 at 6:10 PM, Delapasse, Deanna <
ddelapasse@oceaneering.com> wrote:
> Sorry for all these emails! One more really easy question and I promise
> to stop bothering y'all for a while.
>
> While running locally on my laptop using the simple example my dbname.data
> file (I guess this is my hsqldb) get huge!!! I'm only indexing 30 rows
> over and over (working on some connector enhancements and learning Elastic
> Search), but my dbname.data is already > 11GB.
>
> I don't need to keep any of this data. Is there a fast, easy way to just
> 'reset' my db? I don't mind recreating my output/repo/jobs?
>
> I'm in a meeting right now listening to my boss tell some bigwigs how
> we're got this all figured out (which explains all my stress-filled emails)
> :-).
>
> Thanks!!!
> Deanna
>