Web Services (SOAP) limits
Posted by mkhairul - October 27, 2009 at 12:10:07 am - No CommentsCategories: Tips, Troubleshoot
I’m getting swamped by the task of making an application work with a vendor’s web services. Back in Al-Madinah International University, I did some web service stuffs but that was not an issue as it only sends small amount of data for each transaction.
But now there’s a need to send a lot of data (as much as possible) in one transaction. A single record is at least 500 bytes of data (with all the XML markups), I tried to test by sending an incremental amount of data (starting with 50 records) and worked my way up there, trying to get its limit.
The data is sent back and forth using ajax, when I get a 500 error, I knew it was caused by the amount of data that have to be put in a SOAP envelope.
With 1GB of RAM, I couldn’t even reach 100 records. I tore apart an unused PC in the office and got it up to 2GB and managed to reach 140 records (actually it is 150-160 but, I chose the average limit). Went off to the local pc hardware store and bought a 2GB ram stick. With a total of 3.24GB RAM, I tried it..
I tried sending 200 in one fell swoop and it works. Hopefully tomorrow I can test it more and see how it goes. In the quest to know more about Web Services, here’s some links that I have read.
- High Performance Web Services: Tackling Scalability & Speed
- Large Data Strategies
- Web Services Performance Consideration – Best Practices
- Discover SOAP encoding’s impact on Web service performance
- Improving Web Services Performance (patterns & practices)
- Checklist: Web Services Performance
- Best Practices for Web Service: Part 7, web services infrastructure
No Comments yet »
RSS feed for comments on this post. TrackBack URI
Leave a comment
GimpStyle Theme design by Horacio Bella.
