Hi It totally depends upon your affordability. If you could afford go for bigger RAM, SSD drive and 64 Bit OS.
Benchmark your application, with certain set of docs, how much RAM it takes, Indexing time, Search time etc. Increase the document count and perform benchmarking tasks again. This will provide more information. Everything is directly proportional to number of docs. In my case, I have basic hosting plan and i am happy with the performance. My point is you don't always need fancy hardware. Start with basic and based on the need you could change the plan. Regards Aditya www.findbestopensource.com On Wed, Jul 17, 2013 at 4:55 PM, Ayman Plaha <aymanpl...@gmail.com> wrote: > Thanks Aditya, can I also please get some advice on hosting. > > - What *hosting specs* should I get ? How much RAM ? Considering my > - client application is very simple that just register users to database > and queries SOLR and displays SOLR results. > - simple batch program adds the 1000 OR 2000 documents to SOLR every > second. > > I'm hoping to deploy the code next week, if you guys can give me any other > advice I'd really appreciate that. > > > On Wed, Jul 17, 2013 at 7:07 PM, Aditya <findbestopensou...@gmail.com > >wrote: > > > Hi > > > > It will not affect the performance. We are doing this regularly. If you > do > > optimize and search then there may be some impact. > > > > Regards > > Aditya > > www.findbestopensource.com > > > > > > > > On Wed, Jul 17, 2013 at 12:52 PM, Ayman Plaha <aymanpl...@gmail.com> > > wrote: > > > > > Hey Guys, > > > > > > I've finally finished my Spring Java application that uses SOLR for > > > searches and just had performance related question about SOLR. I'm > > indexing > > > exactly 1000 *OR* 2000 records every second. Every record having 13 > > fields > > > including 'id'. Majority of the fields are solr.StrField (no filters) > > with > > > characters ranging from 5 - 50 in length and one field which is text_t > > > (solr.TextField) which can be of length 100 characters to 2000 > characters > > > and has the following tokenizer and filters > > > > > > - PatternTokenizerFactory > > > - LowerCaseFilterFactory > > > - SynonymFilterFactory > > > - SnowballPorterFilterFactory. > > > > > > > > > I'm not using shards. I was hoping when searches get slow I will > consider > > > this or should I consider this now ? > > > > > > *Questions:* > > > > > > - I'm using SOLR autoCommit (every 15 minutes) with openSearcher set > > as > > > true. I'm not using autoSoftCommit because instant availability of > the > > > documents for search is not necessary and I don't want to chew up > too > > > much > > > memory because I'm consider Cloud hosting. > > > *<autoCommit> > > > ** <maxTime>900000</maxTime> > > > ** <openSearcher>true</openSearcher> > > > **</autoCommit> > > > *will this effect the query performance of the client website if the > > > index grew to 10 million records ? I mean while the commit is > > happening > > > does that *effect the performance of queries* and how will this > effect > > > the queries if the index grew to 10 million records ? > > > - What *hosting specs* should I get ? How much RAM ? Considering my > > > - client application is very simple that just register users to > > database > > > and queries SOLR and displays SOLR results. > > > - simple batch program adds the 1000 OR 2000 documents to SOLR every > > > second. > > > > > > > > > I'm hoping to deploy the code next week, if you guys can give me any > > other > > > advice I'd really appreciate that. > > > > > > Thanks > > > Ayman > > > > > >
