|
Home > Archive > SQL Anywhere Mobile > May 2005 > MobiLink performance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MobiLink performance
|
|
|
| We are using MobiLink 7.0.0.497 as our server and 7.0.313 at our over 300
remote locations. Our synchronization times are not as fast as we would like
them to be and we fully realize that Version 8 was all about performance and
the best thing we could do is upgrade our software. No arguments there.
A couple of questions around our performance:
1) If we upgrade just our server to Version 9 and leave the remotes at
7.0.0.313, can we expect better performance? We have these 300 remotes all
hitting the server at the same time and right now we aren't getting any
performance;
2) We are using the '-zt 1' option on our ML server configuration to hold to
only one processor. I suspect (but am not sure) this is a result of the
Oracle driver we are using to connect via ODBC to our consolidated. But our
ML server box has 4 550 MHz processors! So we are effectively only using 25%
of the processing capacity of that machine!! (I know, I'm shaking my head
too). If we have to stay at version 7, does anybody know of an updated
Oracle driver we can use to get rid of this '-zt 1' option?
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-05-10, 9:23 am |
| A couple of responses to your questions :
1) That's hard to answer without knowing what is causing your performance
issues right now. If the problem is all related to blocking in the
consolidated database during concurrent synchs, then upgrading to v9 without
identifying the issues in your synchronization scripts will result in no
change.
2) Which ODBC driver are you using?
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Doug" < doogie414removethis@
yahoo.com> wrote in message
news:4280a89a$1@foru
ms-1-dub...
> We are using MobiLink 7.0.0.497 as our server and 7.0.313 at our over 300
> remote locations. Our synchronization times are not as fast as we would
like
> them to be and we fully realize that Version 8 was all about performance
and
> the best thing we could do is upgrade our software. No arguments there.
>
> A couple of questions around our performance:
>
> 1) If we upgrade just our server to Version 9 and leave the remotes at
> 7.0.0.313, can we expect better performance? We have these 300 remotes all
> hitting the server at the same time and right now we aren't getting any
> performance;
>
> 2) We are using the '-zt 1' option on our ML server configuration to hold
to
> only one processor. I suspect (but am not sure) this is a result of the
> Oracle driver we are using to connect via ODBC to our consolidated. But
our
> ML server box has 4 550 MHz processors! So we are effectively only using
25%
> of the processing capacity of that machine!! (I know, I'm shaking my head
> too). If we have to stay at version 7, does anybody know of an updated
> Oracle driver we can use to get rid of this '-zt 1' option?
>
>
>
>
>
| |
|
| We are using Oracle driver version 8.01.07.00
There is a Sybase technote that says the 8.1.7.0 Oracle driver is not
recommended. I dunno. Would that be the same as 8.01.07.00 or is it just a
coincidence?
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:4280c4ff$1@foru
ms-1-dub...
> A couple of responses to your questions :
>
> 1) That's hard to answer without knowing what is causing your performance
> issues right now. If the problem is all related to blocking in the
> consolidated database during concurrent synchs, then upgrading to v9
without
> identifying the issues in your synchronization scripts will result in no
> change.
>
> 2) Which ODBC driver are you using?
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Doug" < doogie414removethis@
yahoo.com> wrote in message
> news:4280a89a$1@foru
ms-1-dub...
300[color=darkred]
> like
> and
all[color=darkred]
hold[color=darkred]
> to
> our
> 25%
head[color=darkred]
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-05-10, 11:24 am |
| That's the same driver all right. We have found that all ODBC drivers
created by Oracle will crash when stressed on machines with multiple
processors. That is exactly why the -zt 1 switch was likely recommended.
It wasn't until v702 that we started recommending drivers, and wasn't until
v703 that we started shipping drivers with ASA that we recommended. I'd
hesitate to suggest using a different driver that might allow you to use all
four processors without understanding the decision on why the current driver
you are using was chosen.
If you upgrade the MobiLink server to version 9, we can recommend an ODBC
driver that will allow you to use all four processors. However, I can't
make any guarantees that this will make things faster.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Doug" < doogie414removethis@
yahoo.com> wrote in message
news:4280cb3a$1@foru
ms-1-dub...
> We are using Oracle driver version 8.01.07.00
>
> There is a Sybase technote that says the 8.1.7.0 Oracle driver is not
> recommended. I dunno. Would that be the same as 8.01.07.00 or is it just a
> coincidence?
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4280c4ff$1@foru
ms-1-dub...
performance[color=da
rkred]
> without
> http://www.ianywhere.com/developer/product_manuals
> 300
would[color=darkred]
performance[color=da
rkred]
there.[color=darkred]
> all
any[color=darkred]
> hold
the[color=darkred]
But[color=darkred]
using[color=darkred]
> head
>
>
| |
| Graham Hurst 2005-05-10, 1:24 pm |
| All ODBC drivers we've tested from Oracle have had threading problems.
Using -zt 1 reduced, but did not eliminate, the problem. So we now only
recommend the drivers we supply for Oracle (OEMed from DataDirect,
formerly called Merant and before that Intersolv). You'll get a
recommended driver if you upgrade.
As Reg points out, if contention in your scripts is the performance
bottleneck then upgrading the MobiLink version without changing the
scripts will probably not help much.
However switching from cursor based uploads to statement based uploads
(with version 8 and above IIRC) should double your upload performance.
At least that's what we found.
You can keep using v7 remotes with a v9 ML server, but note that you do
not have to upgrade all remotes at once. If the new remotes need
different scripts than the old remotes, then you can use different
script "versions" (i.e. sets of scripts): the old remotes can keep using
the old scripts, and upgraded remotes use the new scripts.
Cheers,
Graham
Doug wrote:
> We are using Oracle driver version 8.01.07.00
>
> There is a Sybase technote that says the 8.1.7.0 Oracle driver is not
> recommended. I dunno. Would that be the same as 8.01.07.00 or is it just a
> coincidence?
|
|
|
|
|