Max Wanadoo
max.wanadoo at gmail.com
Sat Nov 14 10:27:00 CST 2009
Ok, I thought you were referring to ram available now on common-or-garden PCs. So, we can look forward to physical ram being cheap enough to enable in-vitro processing for millions of records. Hurrah! And goodbye to latency... Max -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: 14 November 2009 16:08 To: 'Discussion concerning Visual Basic and related programming issues.' Subject: Re: [dba-VB] What to do, what to do? Hi Max, Here are theoretical limits I have found info about: Address space 64-bit Windows 32-bit Windows Virtual memory 16 Tb 4 Gb Swap file 512 Tb 16 Tb System cache 1 Tb 1 Gb In practice, mass market motherboards can already handle 64GB(?) - Not enough for JC tasks but this max RAM size limitations should be removed in the near future AFAICG, and Win7 is ready(?) to handle effectively that much RAM.... http://www.nextag.com/64-bit-pci-motherboard/search-html http://www.viva64.com/content/articles/64-bit-development/?f=Application_por t_to_64-bit_platforms_or_never_cackle_till_your_egg_is_laid.html&lang=en&con tent=64-bit-development http://blogs.zdnet.com/hardware/?p=4254 http://www.tomshardware.com/reviews/vista-workshop,1775-3.html Thank you. -- Shamil -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo Sent: Saturday, November 14, 2009 6:39 PM To: 'Discussion concerning Visual Basic and related programming issues.' Subject: Re: [dba-VB] What to do, what to do? Hi Shamil, I understand the logical size bit but for that to be mapped to physical memory requires physical memory to be present. Current there are limits to how much can be installed on the motherboard. 64Bit memory can address the sizes you mentioned but the physical memory doesn't exist, so (presumably) it maps it to the HD, in which case it is not in memory. Have I misunderstood something (it has been known to happen)? Max -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: 14 November 2009 13:46 To: 'Discussion concerning Visual Basic and related programming issues.' Subject: Re: [dba-VB] What to do, what to do? Hi Max, But OS, programs etc. - they all use their own logical address space, which is mapped to (shared (using OS directed swapping)) physical address space: with JC 64bit PC OS image/runtime will be kept in its own physical memory segments - and no swapping will occur, MS SQL image/runtime/data will be (mainly) kept in its own physical memory segments - and almost no swapping will occur, JC's program will have occupied its own physical memory segments - and no swapping will occur... 50 million records assuming every of them is equal to approx. 1KB will consume ~50GB - 64bit PC can have(?) that much RAM allocated for one process, and it all can be addresses directly within this process logical address space. And I have noted that it's currently a "theoretical consideration" but it may become practically achievable in not that far future(?) Correct/wrong? (I must say I didn't get checked how large can be logical address space for a Win7 process running on 64bit PC). Thank you. -- Shamil <<< snipped >>> __________ Information from ESET NOD32 Antivirus, version of virus signature database 4607 (20091114) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com