Re: [Ginp-developers] Scalability and PicCollections

[Justin <ju...@sq...>]

Doug,
	Well the problem ginp was having before was that everytime each web 
user changed directories it re-read all the directory information.  Now 
whenever the system needs the directory information it accesses a 
central read-only cache that is shared among web users.  So if 300 
people pull up the same page there is only one copy of the directory 
information pulled and stored.  When 300 people change directories the 
directory gets read and stored only once, instead of being read and 
stored 300 times as the previous implementation worked.  It also clears 
every two minutes, just so if you add pictures to a directory you don't 
have to restart the server.
	
	When you use start with Eclipse I highly recommend reading through the 
tutorial that comes with it.  It is a great investment timewise.

	I'll see what you're doing on Hibernate in a day or two and then dive 
in there.

Regards,

Justin
Doug Culnane wrote:
> Found no bugs. :-) and it is faster.  Good work.
> You are using techniques that I am finding hard to follow.  This is OK 
> because I think they are obviously good techniques, but you may have to 
> put up with me doing some silly things as I try to get into your code.
> 
> Updated my site to use the HEAD version.  I was having stability 
> problems with the last version so maybe you have fixed this.  Therefore 
> we are running your changes on the main ginp site which is becoming a 
> good stress tester.  The traffic on this site is increasing mainly as a 
> result of some search engine work I did.  SourceForge will hopefully 
> update their stats system soon and we can see how we are doing.  I think 
> we will not get may leads from SF with a activity of 26% which is not 
> too accurate because I think the activity has increased this last 
> month.  The search results always favor the high activity sites.
> 
> Done the xml thing for configuration.  Used XPATH (cool when you 
> understand it) and DTD to specify defaults (seamed a good idea).  Will 
> update documentation if when we are happy with it.  I think it is 
> elegant and good but I am not sure if it is efficient.
> 
> I have broken one of my tests.  This is not good but I am tempted to be 
> aggressive about it and remove the collectionS.jsp page which is mostly 
> not used.  It is a page that allows the user to select the collection.  
> This can be done with a good menu on the collection.jsp page.  I will 
> sleep on this but let me know if you have an opinion about it.
> 
> Started playing with eclipse but got scared and went back to jedit.  It 
> is clearly good but I have to find the time and patience to go thought 
> the tutorials....
> 
> I want to concentrate on Hibernate and the data structure now but again 
> this is a learning curve, that will take time investment before it 
> produces a net gain in productivity.
> 
> All the best,
> 
> Doug
>