Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0029332
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2015-03-18 12:142015-03-31 18:52
ReporterOrekariaView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0029332: Performance: LogClient should not persist until the business layer has persisted

DescriptionPerformance: LogClient should not persist until the business layer has persisted

Saving log to the database while business operations are being held, negatively affects performance

The only benefit would be if the log would be instantly persisted in the server which is not our scenario
Steps To ReproduceIn the 'ob-dal.js' file

Add this lines in the ob.dal.save method:
  OB.Data.localDB.transaction(function (tx) {
        console.error("ob.dal.save " , sql, params);
        try {
          tx.executeSql(sql, params, silentFunction(success), function (txError, e) {
            executeSqlErrorHandler('error', "OB.Dal.save: table", tableName, txError, e);


Go to the WebPOS
Log in
Verify that the log is populated with log client database saves in between business database saves
Proposed SolutionBrain storm

- Save the log to the localStorage and flush it when the 'dataSynchronized' event of the SynchronizationHelper has fired

- Do not use the ob.dal.save for the logclient and remove all the already introduced exceptions because of this
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on design defect 0029277 closedOrekaria Stabilization: Prevent LogClient logging itself in an infinite loop 
has duplicate defect 0029348RR15Q2 closedOrekaria Improve Log Client performance 
has duplicate defect 0028504RR15Q3 closedmarvintm Log Client has a really bad performance and it is really difficult to work 
related to defect 0029363 closedOrekaria Stabilization: LogClient should not flush to the server if the application is busy 
blocks defect 0029396RR15Q3 closedRetail Stabilization: RR15Q3 related 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2015-03-18 12:14 Orekaria New Issue
2015-03-18 12:14 Orekaria Assigned To => Retail
2015-03-18 12:14 Orekaria OBNetwork customer => No
2015-03-18 12:14 Orekaria Triggers an Emergency Pack => No
2015-03-18 12:17 Orekaria Relationship added related to 0029277
2015-03-18 13:31 Orekaria Relationship replaced depends on 0029277
2015-03-18 13:31 Orekaria Relationship added related to 0029102
2015-03-20 17:27 Orekaria Relationship added related to 0029363
2015-03-24 17:51 Orekaria Relationship added blocks 0029348
2015-03-25 17:57 Orekaria Relationship replaced has duplicate 0029348
2015-03-27 17:00 Orekaria Relationship added depends on 0029396
2015-03-31 09:57 Orekaria Relationship added has duplicate 0028504
2015-03-31 18:52 Orekaria Relationship deleted related to 0029102
2015-03-31 19:00 Orekaria Relationship replaced blocks 0029396

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker