>When deleting records, the disk I/O is the bottleneck: The amount of RAM is irrelevant as writes need to be written to disk promptly irrigardless of the amount of RAM. Also note that disk I/O is always challenging on VM ware solutions where the disk is shared amongst several virtual servers. 3rd party products exists to optimize that.
>
>In regards of concurrency problems (deadlock) you need to check what your minimum required ISOLATION_LEVEL is. Read_uncommited does not place locks on records, but therefore might let other queries read inconsistent data because during the transaction. SERIALIZABLE is the most concurrency secure settings, but is much more lickely to cause deadlocks on the database. check the bol documentation for more details,

Thanks