Hi, I don't think we have a formula now, although it is an interesting exercise (it would probably vary widely based on index type, but maybe you have a specific index in mind, like reindexing a lucene property index).
What I wanted to say is that all of aem6x customers go though the same thing: upgrading from 5x to 6x. this implies a full reindex, so I would assume you already have a reference to how long a full reindex might take, even though it's probably a rough estimate (and you'd also have to account for a tiny delta of added content since the upgrade). One random thought: would it be useful to add a sort of 'dry run' call to the indexer, you'd just give it a path (root by default) and a max number of nodes (let's say 100k) and it would output the usual stats (indexed x nodes in .... ms) and throw away the result, this would allow for a sort of guesstimation by type of index, on specific setups. hope this helps, alex On Thu, Feb 4, 2016 at 4:25 AM, Sham Hassan <[email protected]> wrote: > Hi Team, > > > Any appropriate formula we can arrive to calculate how much time it would > take to complete the reindex based on index definition stat from jmx? In > earlier aem5x we use to identify number of nodes+ properties using index > tar file. Then on system performance how much time it takes to complete > 1000 nodes we arrive at rough estimation. In call with customer > perspective we have to give business appropriate downtime & any formula > you could help will be great help for. I an not looking for accurate but > just a rough estimation. > > > Thanks, > Sham >
