Are you doing ANY processing in those loops? if you are doing <@rows>
to just display, it should be fairly fast, but if you are are doing
any kind of processing or calculations in those loops, witango will
just choke. Look in the past some tests I did with randomizing large
arrays in witango.
I do not use SQL 2005, but I can say that using SQL 2000 I did also
see the database seem to not be working as hard, or really taking
advantage of the cpu. Moving to mysql and linux totally solved that
issue. Much faster, much more efficient IMHO.
One of my biggest clients who is still on witango, php port not done
yet, does about 1 million dollars a day in ecommerce through our
application. We have had to bleed every bit of efficiency from the
app and DB. The DBs were setup by MSSQL DBA that were paid a lot of
money. They didn't believe me for a long time, but end of last year,
they finally let me take them to Linux MYSQL, and it was a HUGE boost
in performance. NOTE: I am very good at tuning MYSQL dbs, and I am
sure this could not be as big of a boost if the mysql db was not
tuned properly. Also, the mysql db is completely innodb, not myisam,
in case you are wondering.
To solve large returnsets with processing, the only way to do it is
NOT to use witango. Write an external action in a compiled format, I
use realbasic, to do this. Don't use javabean, because witango also
has a huge bottleneck of reading in lots of data through the javabean
interface.
HTH.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Jun 28, 2007, at 5:50 AM, Wolf, Gene wrote:
I have a situation here that I find very puzzling. So I am going
back to the experts for advice.
We have a few applications that, by their nature, perform
thousands of requests against a SQL database and return thousands
of records. I am quite sure that the coding of the application
isn't as good as it could be and we will look into rewriting it.
Here's our issue: This program, from start to the time it displays
the returning page will take about 3 minutes. (stop groaning). We
are testing this same application on a new box containing 8 dual
core cpu's. I would expect one of those cpus to be pegged while
Witango rips through these thousands of requests. Just the
opposite. The cpus indicate hardly anything happening on the box.
The same is true of SQL server. Even though I am literally throwing
thousands of requests at SQL 2005 I'm seeing virtually no cpu
activity on that box either.
It looks almost like Witango is waiting for something, processes
a request, waits a bit more, processes the next request, waits
again, etc. The environment is Windows Server 2003. One Box is
running Witango 5.5 with 8 dual core processors and the other box
is Windows Server 2003 running SQL Server 2005. Yes, this program
is coded and does some looping but I would still expect it to run
one heck of a lot faster than it is.
Any suggestions?
Gene Wolf
Supervisor, Business Systems
DRS Sensors & Targeting Systems-Optronics
2330 Commerce Park Drive NE
Palm Bay, Florida 32905
Phone: 321-309-0685
321-309-0202 (fax)
Dictionary.com Word of the Day
http://dictionary.reference.com/wordoftheday/
This e-mail, including any attached files, may contain confidential
and privileged information for the sole use of the intended
recipient. Any review, use, distribution, or disclosure by others
is strictly prohibited. If you are not the intended recipient (or
authorized to receive information for the intended recipient),
please contact the sender by reply e-mail and delete all copies of
this message.
"This (document/presentation) may contain technical data as defined
in the International Traffic In Arms Regulations (ITAR) 22 CFR
120.10. Export of this material is restricted by the Arms Export
Control Act (22 U.S.C. 2751 et seq.) and may not be exported to
foreign persons without prior written approval from the U.S.
Department of State."
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
