The reason for this is that we have a fixed record size and do not
index records (the id is the position of the record). This improves
speed and the space will be reclaimed/re-used once the id is reused.
Another thing is that in most use-cases the data size grows more than
it decreases so this has
this a normal behaviour on most RDBMS too.
The size won't decrease until you do some kind of "vacuum full".
At best, the space will be reused when reinserting new data.
--
Ker2x
2010/2/25 Miguel Ángel Águila :
> Hi,
>
> in this part I agree with you but if I had deleted 310.000 nodes from
> 325.
Hi,
in this part I agree with you but if I had deleted 310.000 nodes from
325.000 from de database I think that the database should decrease its
spaces. Before delete the space of the database was 432 MB and after the
delete the database grown until 474 MB, also storing the indexes for
reusing lat
Hi,
Yes those files holds ids that can be reused. If you startup again and
create 310k nodes the id file will shrink and the db file will not
change in size.
Regards,
-Johan
2010/2/25 Miguel Ángel Águila :
> Helo,
> I'm doing a delete operation, in this case I'm deleting 310.000 nodes
> from 325
Helo,
I'm doing a delete operation, in this case I'm deleting 310.000 nodes
from 325.000 nodes. I can delete and after that all works well because
the nodes when I get them only appears the no deleted nodes, but the
size of the folder that contains neo4j database has grown. Specifically
has grown t
5 matches
Mail list logo