Re: [Treebase-devel] Treebase Dev problems

[William P. <wil...@ya...>]

Hi all,

So we continue to get hammered by, I think, someone who is making heavy use of the API. Maybe Mattison can better identify the source of this -- but I don't think it's just higher UI traffic or robot activities because Google Analytics is not showing a jump in activity. While logs show some uncaught exceptions (and Harry is fixing some of these) these are probably not actually causing the slowdown. Rather, objects in memory are probably not being disposed of fast enough and the database is clogging up (direct queries against postgresql are also very slow). 

We need a solution because when TreeBASE bogs down it becomes too slow to submit data, etc.  In fact, right now (11:50PM) TreeBASE doesn't seem to be responding at all.

Can anyone suggest a solution? 

Would this be a possible solution: deploy another VM with Tomcat and another database instance (e.g. take over treebase-stage.nescent.org for this purpose). The database is refreshed nightly from production; the war is rebuilt whenever production is rebuilt; but the two are sufficiently isolated so that heavy API activity doesn't cripple production. Traffic headed to http:://www.treebase.org goes to production. Traffic headed to http://purl.org/phylo/treebase/phylows/ goes to this other instance. 

I guess one possible snag is that when a /phylows/ query includes "format=html", it is jumping to the web page environment -- yet we don't want this API machine to serve web pages to people in any way. So we'd want a /phylows/...?format=html to redirect to production instead. 

bp