300MB has been assigned to the VPC. will try to assign more but dont think it will help much to be honest. everything is worth a try :)
Printable View
300MB has been assigned to the VPC. will try to assign more but dont think it will help much to be honest. everything is worth a try :)
wow
that worked. what the .......... ?!?!?$%$$$$$@@@@£$£@£$£@@
why on earth does it need more than 300MB to do a sort on datetime field?!
could also be a combination of rebooting the VPC image.
Well most of us were telling that VPC has some issues and reboot everything but...:cry:
Glad you solved the problem.Also there is a virtual control center,i cannot recall the name, that has lot's of issues.A friend of mine which is an admin is using it and i went to his home and he almost threw the pc at me.
Virtual...server...private,share something, i cannot recall.
More often than not, greatest performance hindrance of database (any database, oracle, sql server, mysql, etc) is disk I/O. In order to handle volume of data involved (note that additional copies of data generated for read consistency and undo), if all read pages doesn't fit in memory then depending on settings it can be persisted back to disk via system or user tablespaces.. unlike cache/memory access it was retrieved from disk, persisted back to disk (temp/sort store), then retrieved again from disk hence increase in delay and variable duration (depends on current load on disk). Also as much as possible it should be actual/hardware memory, not additional memory via OS page files.Quote:
Originally Posted by Techno
but what didnt make sense was the fact that after restoring the DB on the VPC image, then backing that up and restoring it onto the main PC Again.... it was still showing the problems. the main PC has 2GB of mem
Our Virtual DB Servers run on a phyiscal machine with at least 32GB of memory... We will normallay make 2 virtual machines (sometimes 3) from that. With a min of 16GB for database servers.
yeh sounds about right. something ive said to the client that make sure the server has at least a min of 10GB as i dont think they would be getting many visitors initially.
So you overwrote or stopped original dev instance to run 2nd copy on dev server? If they were running concurrently then they will compete for resources.Quote:
Originally Posted by Techno
Also how was storage layed out? Separate disk controllers to prevent bottleneck? Increasing memory (and database cache) is the easier hardware tune so make sure you can scale that out since rearchitecting storage access later on would be difficult and may require that the database be taken offline.
I stopped the original DB on the dev machine where the DB was copied from the VPC back to the dev (only me accessing the site, its not live yet) and still caused the problem
as for the storage layout - its just a simple DEV box (2GB RAM, SATA HDD, dual core CPU). But like I said, the system works fine on the dev box without the issues that are faced when the DB is copied to the VPC image, which is running on that same dev box :)