You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Nishant Malviya (JIRA)" <je...@portals.apache.org> on 2010/01/21 07:24:57 UTC
[jira] Commented: (JS2-1090) Jetspeed 2.1 derby database becoming
huge.
[ https://issues.apache.org/jira/browse/JS2-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803192#action_12803192 ]
Nishant Malviya commented on JS2-1090:
--------------------------------------
deleting the rows is not releasing the memory, can you suggest further ?
> Jetspeed 2.1 derby database becoming huge.
> ------------------------------------------
>
> Key: JS2-1090
> URL: https://issues.apache.org/jira/browse/JS2-1090
> Project: Jetspeed 2
> Issue Type: Task
> Affects Versions: 2.1.1-RC
> Environment: Windows 2003 SP2
> Reporter: Nishant Malviya
> Fix For: 2.1.1-RC
>
>
> The customer has 2 portlet applications. one with 36 portlets and the second one with only 1 portlet. The customer is complaining that there are a couple .dat files that are taking up a large amount of space:
> ...jetspeed\2.1\database\derby\productiondb\seg0:
> c3c0.dat (12.5 GB)
> c3d0.dat (8.78 GB)
> There are 283 other *.dat files in the same folder of much smaller size. Does this amount of space seem reasonable for the amount of deployed portlets? Is there any way to reduce this size?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org