Long page loading time

Question

Hi,

i have a page with table which contain 230+ text entries and 500+ attachments (pdf file max 3 mb/file).

user feedback that it take more then 5 mins to go into the edit mode, while page load is about 2 min, is that normal?

anyway to reduce the page load time or other method to maintain the information which can be more productive?

Kristian Klima_gtcuat · Answer

@[deleted]

Presumably, it would work exactly as with Google Drive.

A B Linked File Name

You must, of course, assure that users can access the OneDrive files (permissions, access, etc.).

The easiest way is to use some sort of SAML SSO to access both Confluence and your storage.

As for AI... if your AI tooling consumes the DISPLAYED content, it's not an issue. If taps into the Confluence page as such (API), then it's a question to include or exclude specific content. Of course, I'm not familiar with your setup but there are scenarios where this is possible.

unknown · Answer

I tried to educate user by using option 2 and 3, however that requires more work and time for maintenance, furthermore, it might also affect the AI Search feature.

For Option 1, they are using OneDrive to store those files too, any recommendation on using OneDrive to link with Confluence page?

Kristian Klima_gtcuat · Answer

HI @[deleted]

The page must load the ENTIRE content. Working with estimates, 500 x 2MB = 1 GB. One gigabyte needs to be loaded at every time in increments per individual file.

It seems that you're using a confluence page as storage for physical files. That's not what Confluence was built for.

Consider the following options.

Option 1

As you are, it seems, using a table as a quick organizational/referential tool that points to the actual files, I'd store the files in, say, Google Drive and using links in on the Confluence page.

Option 2

* Split the table into logical parts - alphabet or whatever works for what the table is trying convey. 
* Put individual parts of the table into standalone pages - either as plain tables or you can put them inside the excerpt macro. Those pages can live anywhere in the space.
* in the 'master' page, use page include or insert excerpt macro (depending on which you used in step 2) for each and every page/excerpt with your table sections.

This way, viewers should experience faster loading times while editing will take place in the respective standalone pages.

Option 3

Basically step 2 from Option 2 - de-chunk one page into several smaller ones and keep them as child pages of the original page.

__________

Options 1 and 2 preserve the single page entity for viewing.

Personally, I used option 2 when creating a dictionary for mainframe data dictionary elements. It required pages so large Confluence would not save them. So I used page inclusions.