Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] (Protege Server 3.4.3 database-backend) connections to db are not released

Timothy Redmond tredmond at stanford.edu
Thu Mar 4 06:43:47 PST 2010


> It may be though that there is an overhead per project but that this 
> overhead does not grow with the size of the project.  10+M per project 
> is not too bad?

Actually now that I think about this, I think that we found that there 
was a per-project overhead when I analyzed the bioportal.  If I remember 
right it was in a surprising place - code that had to do with a Protege 
gui and was not really needed on a server.

-Timothy


Timothy Redmond wrote:
>
>> However, in our case, the time and memory needed for startup are
>> proportional to the number of projects. With around 35 projects in 
>> server,
>> it takes ~450mb memory space. 
> What happens if you force a garbage collection?  In Java 6 you can do 
> this with jvisualvm and there are ways to do this in Java 5 also.  You 
> may need to force several garbage collections to see what happens.  It 
> may be though that there is an overhead per project but that this 
> overhead does not grow with the size of the project.  10+M per project 
> is not too bad?  It might also be that there is a memory leak that we 
> don't know about.  We do have systems (the BioPortal) with several 
> database projects open.  The thing that is different about your 
> configuration is that your projects import many database projects.  In 
> the BioPortal, all the projects are a single database project with no 
> imports.
>
> I know a bit more about the connection problem but haven't entirely 
> simulated your situation yet.
>
> -Timothy
>
>
>
> sonre wrote:
>> Hi again, we have now another problem. This time with memory.
>> In [1], there is such an expression:
>> "For database projects the speed of loading the system is not directly
>> related to the size of the project. Frames in a database project are 
>> loaded
>> "on demand" and are flushed from the cache when they are no longer 
>> needed
>> and the cache is full"
>>
>> However, in our case, the time and memory needed for startup are
>> proportional to the number of projects. With around 35 projects in 
>> server,
>> it takes ~450mb memory space.
>> Best regards,
>> -soner
>>
>> [1] http://protegewiki.stanford.edu/index.php/Scalability_and_Tuning
>>   
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: 
> http://protege.stanford.edu/doc/faq.html#01a.03




More information about the protege-discussion mailing list