Re: [openstack-dev] [designate] Designate performance issues

2015-03-20 Thread stanzgy
Hi Graham, thanks for your suggestion. But in fact the initial import was a simple while-curl scripts with no concurrency. With this script, a request will not be sent unless previous one gets reponse from designate-api. So I think it's not the rate of initial importing but the number of records

Re: [openstack-dev] [designate] Designate performance issues

2015-03-20 Thread stanzgy
questions) openstack-dev@lists.openstack.org Date: Thursday, March 19, 2015 2:39 AM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: [openstack-dev] [designate] Designate performance issues Hi all. I have setup kilo designate

[openstack-dev] [designate] Designate performance issues

2015-03-19 Thread stanzgy
Hi all. I have setup kilo designate services with powerdns backend and mysql innodb storage in a single node. The services function well at first. However, after inserting 13k A records via API within 3 domains (5k, 5k, 3k for each), the service stops working. designate-api returns 500 and many

Re: [openstack-dev] [designate] Designate performance issues

2015-03-19 Thread Hayes, Graham
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2015 07:41 AM, stanzgy wrote: Hi all. I have setup kilo designate services with powerdns backend and mysql innodb storage in a single node. The services function well at first. However, after inserting 13k A records via API within 3

Re: [openstack-dev] [designate] Designate performance issues

2015-03-19 Thread Vinod Mangalpally
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [designate] Designate performance issues Hi all. I have setup kilo designate services with powerdns backend and mysql innodb storage in a single node. The services function well at first. However, after inserting