Enhancement #5756

Performance improvement to migrating TG import when TG has been preprocessed

Added by Tuukka Lehtonen about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:2015-04-08
Priority:4Due date:2015-04-08
Assignee:Tuukka Lehtonen% Done:

100%

Category:DB clientSpent time:1.00 hour
Target version:1.18.1
Release notes:Fixed TG import performance bottleneck from MigrationStateImpl code path that is used when the imported TG has been preprocessed. The problem caused the code to write the TG into the database using WriteRequest instead of WriteOnlyRequest. This caused the import to be 3-4 times slower than with WriteOnlyRequest.
Tags: perf, db, import
Story points-
Velocity based estimate-
ReleaseSimantics 1.18.1Release relationshipAuto

Description

In class MigrationStateImpl, there is a separate code path for cases where a TG file has been preprocessed (entities renamed etc.) before actually importing the TG file.

In this case the TG importing has been implemented very inefficiently using plain WriteRequests which are much slower than WriteOnlyRequests.

The code should be changed to use WriteOnly requests in the import procedure similarly to the normal case where no TG-preprocessing has been done.

Associated revisions

Revision 31144
Added by Tuukka Lehtonen about 2 years ago

Fixed performance of MigrationStateImpl.getProperty TG import code path where TG preprocessing has taken place prior to the import.

refs #5756

Revision 31145
Added by Tuukka Lehtonen about 2 years ago

Merged trunk@31144 to branches/simantics-1.18 on 2015-04-08 for 1.18.1 release.

refs #5756

History

#1 Updated by Tuukka Lehtonen about 2 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

#2 Updated by Tuukka Lehtonen about 2 years ago

  • Release notes set to Fixed TG import performance bottleneck from MigrationStateImpl code path that is used when the imported TG has been preprocessed. The problem caused the code to write the TG into the database using WriteRequest instead of WriteOnlyRequest.

#3 Updated by Tuukka Lehtonen about 2 years ago

  • Release notes changed from Fixed TG import performance bottleneck from MigrationStateImpl code path that is used when the imported TG has been preprocessed. The problem caused the code to write the TG into the database using WriteRequest instead of WriteOnlyRequest. to Fixed TG import performance bottleneck from MigrationStateImpl code path that is used when the imported TG has been preprocessed. The problem caused the code to write the TG into the database using WriteRequest instead of WriteOnlyRequest. This caused the import to be 3-4 times slower than with WriteOnlyRequest.

Also available in: Atom PDF