Hi David, Good day to you, and thank you for your e-mail.
My secondary storage is connected to the switch using 1 Gbps connection, while my primary storage is connected via a 10 Gbps connection. Unfortunately I don't have 10G NIC cards on my secondary storage. Do you think upgrading my secondary storage's NIC to 10 Gbps will help? May I know how the template and ISOs are being copied, is it through the hypervisor host (e.g. secondary storage --> hypervisor host --> primary storage) or directly (i.e. secondary storage --> primary storage)? My primary storage is not on the same subnet/VLAN as secondary storage, since it's connected to different NIC cards on the hypervisor hosts. If it's a direct connection between secondary storage to primary storage without going to the hypervisor, I might be considering changing my network topology to make the primary and secondary storage to be on the same subnet/VLAN. Looking forward to your reply, thank you. Cheers. On Tue, Jul 23, 2013 at 3:19 AM, David Ortiz <dpor...@outlook.com> wrote: > Meant that question for Indra. Sorry. > > > From: dpor...@outlook.com > > To: users@cloudstack.apache.org > > Subject: RE: CloudStack performance issue > > Date: Mon, 22 Jul 2013 11:34:10 -0400 > > > > Prasanna, > > What kind of network do you use for your setup? Creating a new VM > requires copying the template or ISO over from secondary storage to > primary, so that could be a bottleneck when trying to create multiple VMs > at once. > > -Dave > > > > > Date: Sat, 20 Jul 2013 16:20:08 +0530 > > > From: t...@apache.org > > > To: users@cloudstack.apache.org > > > Subject: Re: CloudStack performance issue > > > > > > On Sat, Jul 20, 2013 at 03:18:12PM +0800, Indra Pramana wrote: > > > > > > > > Where can I start troubleshooting, which logs I need to go through > to find > > > > out the bottleneck? The management-server.log file doesn't show much > > > > anything about the delay. It seems that there is some "locking" > mechanism > > > > and certain processes will need other processes to complete before > they can > > > > start. This is worrying since in a production environment, many > customers > > > > might want to try creating VMs at the same time simultaneously. > > > > > > > > > > The logs of use would be managment-server.log which defaults to DEBUG > > > mode. The logs on the agent (inside KVM host) are default in INFO > > > mode. You can turn them up to DEBUG by altering the log4j config. > > > Apart from that you can also look at libvirt logs. Folks have been > > > tuning the deployment of the VMs on KVM host in another thread on dev@ > > > and in the bug https://issues.apache.org/jira/browse/CLOUDSTACK-3163 > > > > > > let us know if the symptoms are the same and you can bring this up on > > > dev@ with more details. > > > > > > > Any thoughts or feedback on this matter is appreciated. > > > > > > > > Looking forward to your reply, thank you. > > > > > > > > Cheers. > > > > > > -- > > > Prasanna., > > > > > > ------------------------ > > > Powered by BigRock.com > > > > > > >
