Results 1 to 2 of 2

Thread: SOAP Performance Issue Loading Accounts

  1. #1
    artisticlight is offline Member
    Join Date
    Jul 2007
    Posts
    8

    Default SOAP Performance Issue Loading Accounts

    I have been delving into Sugar for the past couple of weeks and have worked on moving account data from an existing order processing system into the Sugar Accounts module. My latest effort was using Sugar's exposed SOAP interface (set_entry) to load 4,000+ records. I am having terrible performance problems.

    It takes approximately 3 minutes for my php script to run and load 50 accounts. If I try to load 100 accounts at a time then I get a timeout error indicating I've exceeded the 300 second maximum. I want to load large volumes of data on a regular basis into accounts and other existing and new modules I plan to create. Is SOAP really viable for this, or is it only good for loading a handful of records at at time?

    I wrote php scripts that load the mysql accounts table directly and I used Jitterbit to load data. They both handled the same 4,000+ records within a matter of seconds.

    Is SOAP that inefficient, or am I missing something?

    I wanted to use the SOAP approach to make sure the data gets loaded properly, including necessary relationships. I don't know that there are published specs regarding those relationship, and I suspect the specs will change over time. Hence, I thought SOAP would ensure that the data got loaded in a manner that Sugar would endorse, and not be as prone to being broke by Sugar upgrades and changes to their data structures.

    Any advice would be appreciated. Use SOAP and live with pathetic performance? Ways to increase SOAP performance? Add data by directly accessing the tables and forget SOAP?

    Thanks in advance for your help.

    Andrew Anderson

  2. #2
    eggsurplus's Avatar
    eggsurplus is offline Sugar Community Member
    Join Date
    Dec 2005
    Location
    Minnesota
    Posts
    2,343

    Default Re: SOAP Performance Issue Loading Accounts

    SOAP is never a good method for converting data (except for the idea of creating items correctly). If you must, then bump up the timeout to a day or so just to be safe. I'd highly recommend doing a database to database conversion like you've done before. If you have a Sugar db set up with sample data you can see how it should be set up. It may take some guessing and checking but most conversions do.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Relating Accounts to Contacts using SOAP API
    By datla27 in forum Developer Help
    Replies: 3
    Last Post: 2007-07-05, 06:36 AM
  2. Replies: 1
    Last Post: 2007-06-27, 04:31 PM
  3. SOAP API: Creating accounts (not users) and projects
    By matt.hocker in forum Developer Help
    Replies: 3
    Last Post: 2007-03-26, 06:49 PM
  4. Replies: 1
    Last Post: 2006-09-11, 03:38 PM
  5. Performance Issue
    By Cturkey in forum Help
    Replies: 2
    Last Post: 2005-07-04, 11:31 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •