CUCM 6.13 - Large Query - API: listUserByName()

Version 1
    This document was generated from CDN thread

    Created by: Keith Lunn on 28-07-2009 01:16:16 PM
    If I have a large cluster and 17,000+ end user accounts and try to select all accounts using API listUserByName OR by using a SQL query against the enduser table, what issue(s) might I ran into?
    Thanks?
     

    Subject: RE: CUCM 6.13 - Large Query - API: listUserByName()
    Replied by: Keith Lunn on 28-07-2009 05:32:28 PM
    Thanks!!!!!!!

    Subject: RE: CUCM 6.13 - Large Query - API: listUserByName()
    Replied by: David Staudt on 28-07-2009 04:01:32 PM
    The way AXL currently works, it will retrieve all of the data from the SQL DB, then populate the entire XML object response in memory before sending it back down to the client via HTTP.  As a result, any very complex or very large request runs the risk of impacting CPU or JVM memory on the Publisher.  You will want to do some testing to ensure your operation does not have a large continuing negative impact on performance when its executing.  If so, you may need to break the request up into smaller units.  For example by requesting users with names starting with A, then a new request with names starting with B, and so on - or using SKIP/FIRST paging with SQL queries.
     
    One specific note, if the XML object returned exceeds 8MB in size (AXL idle) or total outstanding AXL requests exceed 16MB, then requests may be rejected with a specific HTTP code and message.  See the 'What's new in 6.1(3)' blog entry here: http://developer.cisco.com/web/axl/blogroll, and more details in the 7.1(2) AXL documentation.