Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance: Use a CDN for css, javascript, and static images #2647

Closed
raprasad opened this issue Oct 15, 2015 · 7 comments
Closed

Performance: Use a CDN for css, javascript, and static images #2647

raprasad opened this issue Oct 15, 2015 · 7 comments
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Performance & Stability Type: Feature a feature request Type: Suggestion an idea UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@raprasad
Copy link
Contributor

Approximately, 75% of glassfish requests are for static assets including css, js, icons, etc.

fyi: Talk to OpenScholar team about their use of AWS as a CDN

@raprasad raprasad added Type: Feature a feature request UX & UI: Design This issue needs input on the design of the UI and from the product owner Status: Dev Type: Bug a defect labels Oct 15, 2015
@mercecrosas mercecrosas modified the milestone: In Review Nov 30, 2015
@scolapasta scolapasta modified the milestone: Not Assigned to a Release Jan 28, 2016
@kcondon kcondon added Type: Suggestion an idea and removed Type: Bug a defect labels Apr 13, 2016
@pdurbin pdurbin removed the zTriaged label Jun 30, 2017
@mheppler
Copy link
Contributor

mheppler commented Feb 2, 2018

Closing duplicates of this issue and moving comments here.

@pameyer commented on Oct 6, 2017 in issue #4181

Possibly related: #2647 , #1330

7 CSS files in dataverse_template.xhtml, 8 JS files; mix of minified and un-minified. These could potentially be combined (during the build process, not in source) to reduce the number of requests browsers need to make to render the page, which should help with UI performance. The slow step is still likely to be time for glassfish to generate the (x)html.

@mheppler commented on Nov 23, 2015 in issue #2754

Our app serves the user 10 separate CSS files, and 13 separate JS files. Optimizing and efficiently serving these files by combining and compressing these files will help improve client side performance. One common resource that is frequently suggested is the WebUtilities Java library.

@mheppler mheppler changed the title Peformance: Use a CDN for css, javascript, and static images Performance: Use a CDN for css, javascript, and static images Feb 2, 2018
@pameyer
Copy link
Contributor

pameyer commented Feb 2, 2018

@mheppler For this issue, I'd tend to interpret "use CDN" as "not glassfish" vs "use AWS". Does this match your thinking (aka - support but not require external CDN)?

@mheppler
Copy link
Contributor

mheppler commented Feb 2, 2018

That is true. But we could consolidate all of these suggestions into an issue to optimize the use of CSS and JS one way or another.

@pdurbin
Copy link
Member

pdurbin commented Jul 12, 2018

We tried to use a CDN for Bootstrap but due to controversy we removed it (before QA): #4219 (comment)

Sadly, @raprasad is no longer here to advocate for CDNs so I'm closing this issue. A new champion for use of CDNs is very welcome to create a new issue.

@pdurbin pdurbin closed this as completed Jul 12, 2018
@scolapasta
Copy link
Contributor

We removed it with the idea of exploring community thoughts on it (e-mail forthcoming).

@scolapasta scolapasta reopened this Jul 12, 2018
@mheppler
Copy link
Contributor

I reopened UI Performance - investigate improvements to static file handling #4181 with the hopes that a solution can be found, without specifically suggestion one option or another.

@scolapasta I suggest that any outreach you undertake points to that issue, or we open another new issue, to track the community feedback you generate.

@pdurbin
Copy link
Member

pdurbin commented Sep 27, 2023

Not a bad idea but I'm closing this because the JSF UI is going away. We can revisit in the new React repo someday, perhaps: https://github.com/IQSS/dataverse-frontend

@pdurbin pdurbin closed this as completed Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Performance & Stability Type: Feature a feature request Type: Suggestion an idea UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

8 participants