> Assuming an average of 3 seconds, 3000 items x 3 seconds --> 9000 > seconds, around 2 hours and a half! > > It is normal? > I'm running Magnolia 3.6.3 EE, virtualizing on Eclipse, 2 instances > under the same tomcat (5.5.25), both on localhost. > > Other solutions? >
How many public instances do you have? If only one, you can gain some speed (not much tho) by turning off XA activation as you don't need that. Other option would be to change the extraction rule and activate content in bigger chunks rathern then piece by piece ... OTOH if you rely on observation to start your activation it might not be possible for you (Since you get notifications one by one for each piece of content). Possibly unrelated, but I'd like to know why do you activate nodes from data module by observing the changes and then reacting on that, rather then setting "activateImport" of your import handler to "true"? In this case it would be import handler activating your content once the import is done and since it knows of all the content that needs to be pushed to public, you might be able to push it more effectively from there. Yet another option that comes to my mind is that you can run the import on both, author and public instance so you don't need to activate data nodes at all, but that depends on what you are actually doing with those data nodes and whether they aree referenced by uuids or by path only. Cheers, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
