-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
2
-
NOTE: This suggestion is for Confluence Data Center. Using Confluence Cloud? See the corresponding suggestion.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this ticket and weighing it up against our other opportunities, we have decided to transition it to 'Gathering interest' as we don't have plans to work on this in the near term.
Please continue to vote and watch this suggestion if it is important to your team, as we regularly review highly ranked tickets as potential roadmap items.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Most browsers limit the number of simultaneous connections to a particular host. Allowing static resources to be served from a different host may increase performance.
- is duplicated by
-
- Closed
- relates to
-
- Closed
[CONFSERVER-18265] Add the ability to serve static resources like images from hosts other than the one in the base URL
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this ticket and weighing it up against our other opportunities, we have decided to transition it to 'Gathering interest' as we don't have plans to work on this in the near term.
Please continue to vote and watch this suggestion if it is important to your team, as we regularly review highly ranked tickets as potential roadmap items.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.
We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.
Cheers,
Confluence Product Management
Aleksandar Lazic
added a comment - Based on my Support-Request https://support.atlassian.com/browse/CSP-62984 I believe that the delivering of static content (images, css-files, js-files, attachments, ...) from the webserver (first tier, in a Multitier architecture) will have a massive improvement of the performance.
An example set-up could look like this
From my point of view, there are many different solutions possible to achieve this target.
Here are some example solutions:
- X-Sendfile
- try_file
- mod_rewrite => '-s' (is regular file, with size)
- Url Aliases nginx apache httpd
- and a lot of other possibilities depend on web server
Some of the solutions above do not scale well with NAS Set-ups 
( e.g. sendfile based solutions)
To make the above possible the application server (jira, confluence, …) must offer the option to stage out defined content to the file system.
From my point of view there are different solutions possible for the appserver.
Here are some example solutions:
- manual staging based on User wish (e.g.: staging button)
- automatic staging based onUpdate event
- automatic staging based on time-stamp (e.g. Service)
- automatic staging based on Version (e.g. Service)
I prefer the first two options from a user point of view .
The second solution has some pitfalls.
For example when a user makes temporary saves for his content.
I would be happy if atlassian products could offer such options to increase the performance.
Aleksandar Lazic
added a comment - Based on my Support-Request https://support.atlassian.com/browse/CSP-62984 I believe that the delivering of static content (images, css-files, js-files, attachments, ...) from the webserver (first tier, in a Multitier architecture ) will have a massive improvement of the performance.
An example set-up could look like this
From my point of view, there are many different solutions possible to achieve this target.
Here are some example solutions:
X-Sendfile
try_file
mod_rewrite => '-s' (is regular file, with size)
Url Aliases nginx apache httpd
and a lot of other possibilities depend on web server
Some of the solutions above do not scale well with NAS Set-ups ( e.g. sendfile based solutions)
To make the above possible the application server (jira, confluence, …) must offer the option to stage out defined content to the file system.
From my point of view there are different solutions possible for the appserver.
Here are some example solutions:
manual staging based on User wish (e.g.: staging button)
automatic staging based onUpdate event
automatic staging based on time-stamp (e.g. Service)
automatic staging based on Version (e.g. Service)
I prefer the first two options from a user point of view .
The second solution has some pitfalls.
For example when a user makes temporary saves for his content.
I would be happy if atlassian products could offer such options to increase the performance.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center