Title: Witango v5 Server on X performance
[This is an excerpt from a post to WE about the server performance. In the spirit of “leaking” information, I thought some of you mac heads may want to read it.]

I have been working through most of the code I have written over the last year or so, and am noticing excellent performance with v5.036.

Some notes:

Image Serving:
I wanted to seriously test the threading and binary retrieval/serving of the new server. I used first the eventpix site as a test since I have the code written to show many thumbnails per page. I added some code to make the app browse up to 100 thumbnails at a time, which is a ridiculous amount. Then cleared all browser cache to verify that the images would have to be pulled from the DBMS by Tango. The structure of this app is that it calls a taf “Event.taf?_function=list&eventid=123” which allows a user to browse an event and shows a user configurable number of thumbnails per page. If 100 thumbnails are chosen, then the taf “thumb.taf?imageid=123???” gets requested 100 times on this single page. Each thumbnail is about 5k.
On my production servers, I found that allowing more than 25 thumbs per page caused severe problems. There would be broken images, and sometimes the images would just be blank. I set my test server running v5.036 to show 100, and one of my production servers running v4.05.047 to show 100. I picked an event with 1680 images so that I could pop through 16 pages of 100 images. The v4 server would take about 9-11 seconds to show the 100 images, and after a few pages, would eventually choke. Either broken images or blank images.
On v5, the server took about 5 seconds consistently to show the 100 images, and I have several times paged through all 16 pages without losing any images. It was also more consistent and fluid, no strange “hangs” that you see so much in v4.
Also, some other observations. v4 opened 8 connections to my DBMS to serve the 100 images per page, where v5 used only 4. Much more efficient.

Serving Larger binary files:
I have other apps, one in particular, that serve binary files like PDFs. This one app, a Technical Information Library, allows the customer to administrate the library, and upload text and info about a pdf, and upload the pdf to the site. All information is stored in the DBMS to control download which allows the customer to generate leads from the downloading of information(pdfs). The largest file being served is a 2.7mb pdf catalog. The data is retrieved, the http header is modified, and the pdf is pushed directly to the user via content-disposition=attachment;filename=whatever. If I download this file from v4, there is a lag from the moment I click the link to execute the download until the file actually starts downloading. The lag is about 13 seconds for this size of file, and is proportional to the size of file downloaded. On v5 the lag is only 1 second. Quite a bit of difference. Well done.

--

Robert Garcia
BigHead Technology
2781 N Carlmont Pl
Simi Valley, CA 93065
Phone 805.501.1390
Fax 805.522.8557
http://www.bighead.net/
[EMAIL PROTECTED]

Reply via email to