> - whats the best way to use solr to get the best performance for an huge > portal with >5000 users that might expense fastly?
5000 users: 200 TPS, for instance, equal to 1200 concurrent users (each user makes 1 request per minute); so that single SOLR instance is more than enough. Why 200TPS? It is bottom line, for fuzzy search (I recently improved it). In real life, real hardware, >1000TPS (using caching, not frequently using fuzzy search, etc.) which is equal to 60000 concurrent users, subsequently to more than 600,000 of total users. The rest depends on your design... If you have separate portals A, B, C - create a field with values A, B, C. Liferay Portal nicely integrates with SOLR... each kind of "Portlet" object (Forum Post, Document, Journal Article, etc.) can implement "searchable" and be automatically indexed. But Liferay is Java-based, JSR-168, JSR-286 (and it supports PHP-portlets, but I never tried). Fuad Efendi +1 416-993-2060 http://www.linkedin.com/in/liferay > -----Original Message----- > From: Peter [mailto:zarato...@gmx.net] > Sent: January-16-10 10:17 AM > To: solr-user@lucene.apache.org > Subject: Fundamental questions of how to build up solr for huge portals > > Hello! > > Our team wants to use solr for an community portal built up out of 3 and > more sub portals. We are unsure in which way we sould build up the whole > architecture, because we have more than one portal and we want to make > them all connected and searchable by solr. Could some experts help us on > these questions? > > - whats the best way to use solr to get the best performance for an huge > portal with >5000 users that might expense fastly? > - which client to use (Java,PHP...)? Now the portal is almost PHP/MySQL > based. But we want to make solr as best as it could be in all ways > (performace, accesibility, way of good programming, using the whole > features of lucene - like tagging, facetting and so on...) > > > We are thankful of every suggestions :) > > Thanks, > Peter
