x Want to participate? Join the group to interact
  • Replies 9 replies
  • Subscribers 104 subscribers
  • Views 4255 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
758
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
microtek

Processing Speed on Big Data

Posted By

Hi,


I would like to get some information on How Sage 300 deal with large number of transaction for benchmark purpose. I got a prospect asking that when processing an OE Invoices they are going to have like 200+ shipment with 8 details line in average per shipment document. In total there will be at least 1600 Line to be process on Invoices. Does any one experience on this kind of transaction? If Yes what would be the time consumed start from Accepting the selected document until the posting is completed? Please share information. Thank you

  • We have clients that exceed that in terms of detail lines and volume - they're not complaining.
  • in reply to Ettienne Schwagele
    Dear Ettienne,

    May I know how long does it takes to process those document if you have the data. Thanks
  • in reply to microtek
    Don't know - don't have the data. Do some testing on your side.
  • We our data process is an order of magnitude larger. Our day end has been customized slightly and runs after business hours. Typically it takes 30 - 45 minutes to process.

    A lot of this is going to be related to what gear you've got. If your metal is not up to the task, processing could take forever.
  • in reply to data-splunker
    wow so that was poorly written. Sorry guys.

    If you would like to know what our backend hardware is I'll be happy to let you know. We're currently averaging 2,300 SQL Exec's per second.
  • in reply to data-splunker
    Dear Data-splunker,

    Yes would be nice if you could share some information. the 30-45Minutes you mention is for the day end processing or the data processing? Thanks
  • in reply to microtek
    30-45 minutes is for the Day end Processing that usually takes place between 12:30am or 1:30am dependent on the day. We have a custom script in place that exports then imports our vendor costing tables to ensure our negotiated vendor pricing doesn't get mangled by Day End.

    With the below configuration, running Accpac from anywhere in the line is as fast as anywhere else and we're processing 1000's of transactions a day. Our only complaint is the speed in which the new .NET Crystal Reports Engine runs (it's dead slow) - Sage has confirmed with us that on their own hardware it takes upto 8 seconds to load.

    Ok so here's what we have:

    SQL Server (Dedicated)
    Dual Xeon E5645 2.4Ghz Hyperthreaded (24 logical cores)
    96GB Ram (so we can load the entire DB in RAM)
    1 1TB Raid 10 SAS 10k
    1 3TB Raid 5 SAS 10k
    LSI Raid Card

    Sage300 Shared Directory Server (doubles as domain controller)
    Dual Xeon E5-2620 v2 2.1Ghz (12 Logical cores)
    32GB Ram
    500GB Raid 10 SAS 7.2k
    1TB Raid 10 SAS 7.2k
    LSI Raid Card

    Terminal Server (The "Piece De Resistance") Usually 40 - 60 users per Terminal Server
    Dual Xeon E5-2470 2.3Ghz Hyperthreaded (32 Logical Cores)
    48GB Ram
    1TB Raid 5 SAS 7.2k
    LSI Raid Card
  • in reply to data-splunker
    Great, Thanks for the sharing.

  • so far is there any solution for this Big Database of Day end process yet ?

    Regards,
    Sakada

*Community Hub is the new name for Sage City