Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How fast is fast

Status
Not open for further replies.

jjgraf

Programmer
Joined
Aug 19, 2001
Messages
237
Location
US
I’m writing a com object that will be a web service and a standard DCOM used by desktop applications. I been trying to improve its performance.

Specs:
Database: SQL Server
All Data checking is done by COM
Can not use FoxPro Database objects or Remote Views

So I have been using Sql Pass Through to get blank cursors and then turn them into Updateable cursors.

To add 5 master records in Return Merchandise Authorization and 100 detail records along with a log table describes what user do what and when that’s 1000 records in 10.898 seconds. Which is 0.010898 seconds per record.

Since I started I was able to increase performance by half, should i be looking for more ways to squeeze more speed out of this?
 
Answers to these kinds of questions tend to be meaningless. Without knowing all the hardware, software and data structures involved (not to mention the actual code!), a number like "0.010898 seconds per record" has no context. That's really fast if you are running SQL Server 6.0, on NetBui at 10mbps, running VFP 3.0 with 4000 character records on PII workstations and servers!

The real questions are - "Do you need more speed? Why?"

Rick
 
Hardware:
client:
RAM: 128
CPU: 400 Celeron
VFP: 7.0 sp1

SQL test server
RAM: 196
CPU: 350 PII
SERVER W2K
SqlServer 2000 SP 2

header record has 241 characters
detail record 320 plus 2 text fields in my test have 100 characters each
log table has 198 characters

Total of 639 characters

What I do is create a local updateable cursors then send a tableupdate() when finished adding records

Network is 100mb

In my testing there is an associated 0.35 to 0.623 seconds of over head to make an ODBC connection and make the cursor updateable.

Reason to make faster because we all want the fastest possible code we can have.
 
On the issue of reason for speeding up. In my place of work I let the users decide if the code is fast enough. If they scream and ball, then I factorise it and use all the tricks I know.

But this takes time as there are a few paths to go down and you have to go down them all to get the best. Is it worth it? In a demorcacy the voter decides, let the user decide!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top