[
https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20127#action_20127
]
Peter Dietz commented on DS-871:
--------------------------------
I'm at an impasse too. You can disable cache on XMLUI all-together, but you
don't want to do that. You can disable cache by changing
https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/sitemap.xmap#L196
to type="noncaching". This is the same file as
[dspace]/webapps/xmlui/sitemap.xmap.
While load testing (10 concurrent users in JMeter), a cached community-list
takes only 110ms on average. Yet an uncached community-list is upwards of 5
seconds per request. Most requests without caching become unbearable for a
production system.
Some pages in DSpace are caching and invalidating properly though. When you
edit the metadata for an item, and then view the item page, the content changes
to reflect your changes. So various transformers in xmlui need to be verified
that they are properly checking the validity of the cache, and invalidating the
cache when events have changed the content. Additionally, it is possible that
some bug higher up has cached the entire pipeline, and ignoring an individual
transformers validity.
> XMLUI caches community / collection page which doesn't show a recently
> submitted item immediately
> -------------------------------------------------------------------------------------------------
>
> Key: DS-871
> URL: https://jira.duraspace.org/browse/DS-871
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.7.0, 1.7.1
> Reporter: Peter Dietz
>
> With discovery disabled in xmlui, a recently submitted item does not show on
> the recently submitted items list for the collection or community page, until
> the page cache expires. This may be by design, but it is a route that a user
> may be expecting to find their recently submitted item.
> Perhaps on submission, the cache for the parent container pages can be
> invalidated so that the next page view of it will get the recently submitted
> item in the list.
> To reproduce, in xmlui (tested with discovery off), view a collection page,
> then submit a new item to that collection, and go back to that collection
> page after submission. Continuously refreshing the page will not show the new
> item, unless a user tries to hard-clear the xmlui cache. Such as appending
> junk to the url as a parameter. i.e.
> servername.com/handle/123456789/1234?random-text
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
