CQ TarPM stop automatic optimization | Community
Skip to main content
F
Fisherwoon
October 16, 2015
Solved

CQ TarPM stop automatic optimization

  • October 16, 2015
  • 3 replies
  • 816 views

I using CQ5.6.1 and CRX 2.4.23.

In workspace.xml, i have set autoOptimizaAt as "" (empty string).

<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager">
    <param name="autoOptimizeAt" value="" />
</PersistenceManager>

 

But it still continue running and it dint stop after default time.

Do i need set the same config for repository.xml?

I want to temporary stop run TarPM.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

it's best you do the changes in both. Akthough the definition in the workspace.xml should be authoritative.

Jörg

3 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

For details how to configure the TarOptimization, please also refer to [1]. I wouldn't recommend to turn off optimization, as the disk consumption will increase dramatically (depending on the activities on the repo).

My usual recommendation for operation is to disable TarOptimization in the configuration and always trigger it externally (Unix cron or Windows scheduler) via the "optimize.tar" file (also see [1]). Then you are much more flexible and you can temporarily disable it for 1 day or so. But never disable it for days or even weeks!

Jörg

 

[1] http://helpx.adobe.com/experience-manager/kb/TarPMOptimization.html

F
FisherwoonAuthor
October 16, 2015

Hi Jörg,

May i know exactly where autoOptimizeAt i should set at in order to disable TarOptimization? For example in which file?

And i also prefer use crontab to perform TarOptimization.

Thanks
Fisher

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

it's best you do the changes in both. Akthough the definition in the workspace.xml should be authoritative.

Jörg

Terms & ConditionsAccessibility statement

Loading footer...