[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Saravanan Paramasivan updated MAGNOLIA-4761:
--------------------------------------------

    Visible to: [ssubash]

> Publishing taking too much time
> -------------------------------
>
>                 Key: MAGNOLIA-4761
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4761
>             Project: Magnolia
>          Issue Type: Improvement
>      Security Level: Public
>          Components: workflow
>    Affects Versions: 4.5.3
>         Environment: RHEL QUAD processor 15G RAM with tomcat heap size of 
> tomcat 6GB
>            Reporter: Saravanan Paramasivan
>            Priority: Major
>
> We are using Magnolia 4.5.3 with MySQL (1 author + 2 public clustered). Our 
> data size may be approx 40GB (5 GB sqldump + 35 GB repo folder)
> Out of all publishing, 15GB took more than 5 days to publish. 
> Usecase: From third party, we will pull information and persist in the 
> content nodes. We do this as nightly job and publish the data to public node 
> by marrying the data and webpages. We are using Recursive command to do thia 
> auto publish activity.
> There is no problem in publishing the nodes at all. But it's taking time to 
> publish huge chunk of data. Kindly let us know the improvement 
> areas/suggestion which can make our job faster
> SQL dump: http://ftp2.sdxi.com/CGAuto/forMagnolia/magnoliaRepo/ - Reach out 
> to Chrisitian for username/password

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to