Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Initial load performance is very poor. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    When I initially synchronize from my datasource to my local SQLCE database, the time taken is 10 minutes. Examined the performance, and it appears a lot of time is taken within the MSSync services with datatables... and in addition, it's not using SQLCEResultSets to insert data.

    So, I wrote my own initial population, and it takes 2minutes 30 seconds for the same data.

    I am hoping that some of hte inefficiencies will be ironed out in the full release, but in the meantime, I am planning on using my initial load function and thereafter using MSSync to make the small changes...

    Mark.
    • Moved by Max Wang_1983 Friday, April 22, 2011 10:27 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Monday, July 2, 2007 10:04 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Mark for sharing the great info with us.

     

    by reading your msg, I think you hit the same issue as I mentioned in my previous post. the issue is acutally in ADO.NET code and we are going to fix it with the SSCE 3.5 SP1 release.

     

    Good to see you find the way to use the sqlceresultset to work around this perf issue.

     

    thanks

    Yunwen

    Wednesday, July 11, 2007 4:06 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mark,

     

    We are aware of a perf issue with this release and will be address them in the near future.

     

    I would appreciate if you can share out your table schemas, number of rows in them etc with us so we can try out your schema also for testing purpose. if the schema is confidential, could you let us know the number of columns in the table ?

     

    thanks

    Yunwen

    Monday, July 9, 2007 5:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi - i guess schema is confidential. But I can give you a good idea:

    Will be synchronising 25-40 tables.

    About 10 of these are major entity tables (up to 90 columns), and will have up to 100,000 rows.

    Others are relationship tables and will have only 2-3 columns, but will have 500,000+ rows.

    In my testing, the SqlCeResultset was far faster than any other way to insert data to an SQLCE database.

    Also, interestingly, there was performance gain to add the primary Key and other indexes _after_ intial population.

    Mark.
    Tuesday, July 10, 2007 10:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Mark for sharing the great info with us.

     

    by reading your msg, I think you hit the same issue as I mentioned in my previous post. the issue is acutally in ADO.NET code and we are going to fix it with the SSCE 3.5 SP1 release.

     

    Good to see you find the way to use the sqlceresultset to work around this perf issue.

     

    thanks

    Yunwen

    Wednesday, July 11, 2007 4:06 PM
    Moderator