On Mar 13, 2008, at 2:18 AM, Ryan Gardner wrote:
On Mar 13, 2008, at 12:00 AM, Will Scheidegger wrote:
Well, flushing the cache many times _is_ normal since Magnolia
flushes after each page it publishes. Now if you publish a whole
site with many pages there will be a lot of flushing. This is sure
one thing that could be optimized in future versions.
I only activate one node, no sub-nodes.
In general I think publishing even single pages has too big of an
impact on the performance of the system. I don't know exactly what
the big work is, that Magnolia is doing, but I would guess that
there is room for improvement here.
Regards,
Will
I was assuming he was talking about just one node - but yeah - if
he's doing "including subpages" on a top-level node, that would
make sense.
I've never seen the problem of the site coming to a crawl when I'm
activating. Are you referring to the Author instance or the public
instance?
Author instance.
I'm usually tailing the server logs when I'm doing lots of work, so
I'm seeing the activation as it is happening - so I don't care that
the author instance becomes unresponsive.
For a reference of a good implementation of progress-bars and such,
I was playing around with Artifactory the other night, and the
newest version uses some cool ajax stuff to show progress bars on
file uploads.. etc. - and does a very good job of showing progress.
(There are still a few things that it could definitely improve upon
- but the progress bars are very good - some of the best I've seen)
- As a side bonus, anyone working with a team doing Maven builds
would benefit greatly
Thanks,
Po Ki
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
