Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0029332Retail ModulesWeb POSpublic2015-03-18 12:142015-03-31 18:52
ReporterOrekaria 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0029332: 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
Additional Information
TagsNo tags attached.
Relationships
depends on design defect 0029277 closed Orekaria Stabilization: Prevent LogClient logging itself in an infinite loop 
has duplicate defect 0029348RR15Q2 closed Orekaria Improve Log Client performance 
has duplicate defect 0028504RR15Q3 closed marvintm Log Client has a really bad performance and it is really difficult to work 
related to defect 0029363 closed Orekaria Stabilization: LogClient should not flush to the server if the application is busy 
blocks defect 0029396RR15Q3 closed Retail Stabilization: RR15Q3 related 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-03-18 12:14OrekariaNew Issue
2015-03-18 12:14OrekariaAssigned To => Retail
2015-03-18 12:14OrekariaTriggers an Emergency Pack => No
2015-03-18 12:17OrekariaRelationship addedrelated to 0029277
2015-03-18 13:31OrekariaRelationship replaceddepends on 0029277
2015-03-18 13:31OrekariaRelationship addedrelated to 0029102
2015-03-20 17:27OrekariaRelationship addedrelated to 0029363
2015-03-24 17:51OrekariaRelationship addedblocks 0029348
2015-03-25 17:57OrekariaRelationship replacedhas duplicate 0029348
2015-03-27 17:00OrekariaRelationship addeddepends on 0029396
2015-03-31 09:57OrekariaRelationship addedhas duplicate 0028504
2015-03-31 18:52OrekariaRelationship deletedrelated to 0029102
2015-03-31 19:00OrekariaRelationship replacedblocks 0029396

There are no notes attached to this issue.