My experience shows that working with a 300Mhz/192Mb RAM works fine in paralel with NetBeans/Tomcat for development purposes. To run in this config you should make some "modifications" in default configuration (reduce connections, buffers, etc).
This type of configuration IMHO should not be changed for a normal database size (about 1Gb-2Gb) in production (I've several mid-sized clients in this limit - with about 100 users). To greater databases you probaly will need to make some tunning, but nothing "too hard". And yes: if your database will run alone in Win2K, and you make some restrictions in configurations that affect memory consumption, you'll run fine in 64Mb. Personally, I'll not recomend you this. Good luck. Don't forget to share your experiences (when they occur) with the list. Edson Richter ----- Original Message ----- From: "Stephen Gutknecht (SAPDB)" <[EMAIL PROTECTED]> To: "Ivar Zapata" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, October 06, 2002 5:42 PM Subject: RE: Miniimun RAM requirements in Windows 2000 > I'm sure the SAPDB people can give you a more formal answer... But I'll give > you my informal one. > > In my experience, Most "System requirements on the box of software" are a > joke. They are more about "don't bother purchasing this if you don't know > what you are doing" than any practical information. > > But based on my testing... SAPDB will start and work with almost ANY amount > of RAM. Windows 2000 has virtual memory and with just page everything. As > long as you have enough RAM for Windows 2000 to boot, you should be able to > run SAPDB. > > That being said, performance will suffer if you try to run Windows 2000 + > SAPDB on a system with only 64MB of RAM. > > Going by my simple observations, I believe the SAPDB kernel itself takes > about 32MB of RAM usage, plus your data cache size. Using the TST (demo) > database as an example, it takes around 42MB of the virtual memory space > (28MB non-paged). > > Of course, if you plan a database (on disk) of substantial size, you may > need to plan for much more than that to accommodate the data cache. It is > all about your application needs. > > For a small single-user dedicated application, I could see Windows 2000 > Professional + SAPDB running very well 128MB of RAM, likely even 96MB. > Multi-user server, other programs running at same time, large datasets, now > things change... > > I've load tested a e-commerce web site using Windows 2000 + IIS + SAPDB in > 128MB and things worked very well. Just depends how well optimized your > database design is. Small primary keeys (integers and not 32 character > strings), etc. > > Stephen Gutknecht > > > > -----Original Message----- > From: Ivar Zapata [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 4:45 PM > To: [EMAIL PROTECTED] > Subject: Miniimun RAM requirements in Windows 2000 > > > I've gone through the documentation and didn't find any clue. > > > �Hints? > > > > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > > --- Email foi verificado quanto a exist�ncia de virus antes de seu envio, e n�o h� virus. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.394 / Virus Database: 224 - Release Date: 03/10/2002 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
