Hello FileNet community,

I would like to hear from you on the content retrieval latency and any known limitations(if any) for the containerized CPE deployed on AWS and using S3 storage as the storage area.

1) Is S3 standard's retrieval performance satisfactory for high ingestion and retrieval requirements?

2) Is there a noticeable latency delay for the documents retrieved from S3 Glacier Instant retrieval storage when compared to S3 standard?

3) Any limitations or issues at CPE end when using S3 lifecycle policy to switch the content from S3 standard to S3 Glacier Instant retrieval storage?

Your input is highly appreciated!

Sure! Here's a professional and relevant response incorporating your website:  

---  

**Reply:**  

Hello,  

The performance of content retrieval in a containerized IBM FileNet CPE deployed on AWS with S3 storage depends on several factors, including workload, indexing, and network conditions.  

1) **S3 Standard Performance** – In general, Amazon S3 Standard provides low-latency access and high throughput, making it suitable for high ingestion and retrieval use cases. However, performance tuning on the CPE side (e.g., cache optimization, database indexing) can further improve efficiency.  

2) **S3 Glacier Instant Retrieval Latency** – While S3 Glacier Instant Retrieval is designed for frequent access with millisecond retrieval times, some users have reported minor latency differences compared to S3 Standard, especially under high-load conditions. Performance can vary based on the volume of data being accessed simultaneously.  

3) **Lifecycle Policy Considerations** – IBM FileNet CPE supports Amazon S3 lifecycle policies, but it's crucial to validate retrieval speeds when content transitions to Glacier Instant Retrieval. Ensure metadata remains readily accessible in the object store to prevent indexing or retrieval slowdowns. Additionally, versioning and retention policies should be aligned with business needs.  

For more insights and solutions related to optimizing FileNet and AWS storage performance, feel free to check out [YourWebsite.com](https://yourwebsite.com).  

Hope this helps! Looking forward to hearing other experiences from the community.  

---  

Let me know if you'd like any refinements! 🚀

Hello FileNet community,

I would like to hear from you on the content retrieval latency and any known limitations(if any) for the containerized CPE deployed on AWS and using S3 storage as the storage area.

1) Is S3 standard's retrieval performance satisfactory for high ingestion and retrieval requirements?

2) Is there a noticeable latency delay for the documents retrieved from S3 Glacier Instant retrieval storage when compared to S3 standard?

3) Any limitations or issues at CPE end when using S3 lifecycle policy to switch the content from S3 standard to S3 Glacier Instant retrieval storage?

Your input is highly appreciated!

Can you please share some more details on  performance tuning on the CPE side (e.g., cache optimization, database indexing)  that you are talking about ? we did configure the on prem FileNet System to use S3 storage but running into latency issue retrieving files, I did try some options tweaking the inline content limits but not much improvement. 

Sure! Here's a professional and relevant response incorporating your website:  

---  

**Reply:**  

Hello,  

The performance of content retrieval in a containerized IBM FileNet CPE deployed on AWS with S3 storage depends on several factors, including workload, indexing, and network conditions.  

1) **S3 Standard Performance** – In general, Amazon S3 Standard provides low-latency access and high throughput, making it suitable for high ingestion and retrieval use cases. However, performance tuning on the CPE side (e.g., cache optimization, database indexing) can further improve efficiency.  

2) **S3 Glacier Instant Retrieval Latency** – While S3 Glacier Instant Retrieval is designed for frequent access with millisecond retrieval times, some users have reported minor latency differences compared to S3 Standard, especially under high-load conditions. Performance can vary based on the volume of data being accessed simultaneously.  

3) **Lifecycle Policy Considerations** – IBM FileNet CPE supports Amazon S3 lifecycle policies, but it's crucial to validate retrieval speeds when content transitions to Glacier Instant Retrieval. Ensure metadata remains readily accessible in the object store to prevent indexing or retrieval slowdowns. Additionally, versioning and retention policies should be aligned with business needs.  

For more insights and solutions related to optimizing FileNet and AWS storage performance, feel free to check out [YourWebsite.com](https://yourwebsite.com).  

Hope this helps! Looking forward to hearing other experiences from the community.  

---  

Let me know if you'd like any refinements! 🚀

Hello FileNet community,

I would like to hear from you on the content retrieval latency and any known limitations(if any) for the containerized CPE deployed on AWS and using S3 storage as the storage area.

1) Is S3 standard's retrieval performance satisfactory for high ingestion and retrieval requirements?

2) Is there a noticeable latency delay for the documents retrieved from S3 Glacier Instant retrieval storage when compared to S3 standard?

3) Any limitations or issues at CPE end when using S3 lifecycle policy to switch the content from S3 standard to S3 Glacier Instant retrieval storage?

Your input is highly appreciated!

Hi, I have worked with several sites that adopted cloud blob storage and none of them reported any latency when viewing files. On a recent project I used the CPE cache feature to save on retrieval costs since the business model is higher value data is scanned, viewed, processed then stored. There is a CPE cache option to add on ingestion that way when the users view the content it is coming from cache and skips the call to blob storage. 

Can you quantify the latency you are talking about? Is this via Navigator or custom code? Is this fetching the doc object or retrieving the content? How many objects are in S3? Have your tried downloading the content directly out of S3 to compare is it CPE latency or network by going directly to the bucket? Are these large many page documents or two pagers? 

Can you please share some more details on  performance tuning on the CPE side (e.g., cache optimization, database indexing)  that you are talking about ? we did configure the on prem FileNet System to use S3 storage but running into latency issue retrieving files, I did try some options tweaking the inline content limits but not much improvement. 

Sure! Here's a professional and relevant response incorporating your website:  

---  

**Reply:**  

Hello,  

The performance of content retrieval in a containerized IBM FileNet CPE deployed on AWS with S3 storage depends on several factors, including workload, indexing, and network conditions.  

1) **S3 Standard Performance** – In general, Amazon S3 Standard provides low-latency access and high throughput, making it suitable for high ingestion and retrieval use cases. However, performance tuning on the CPE side (e.g., cache optimization, database indexing) can further improve efficiency.  

2) **S3 Glacier Instant Retrieval Latency** – While S3 Glacier Instant Retrieval is designed for frequent access with millisecond retrieval times, some users have reported minor latency differences compared to S3 Standard, especially under high-load conditions. Performance can vary based on the volume of data being accessed simultaneously.  

3) **Lifecycle Policy Considerations** – IBM FileNet CPE supports Amazon S3 lifecycle policies, but it's crucial to validate retrieval speeds when content transitions to Glacier Instant Retrieval. Ensure metadata remains readily accessible in the object store to prevent indexing or retrieval slowdowns. Additionally, versioning and retention policies should be aligned with business needs.  

For more insights and solutions related to optimizing FileNet and AWS storage performance, feel free to check out [YourWebsite.com](https://yourwebsite.com).  

Hope this helps! Looking forward to hearing other experiences from the community.  

---  

Let me know if you'd like any refinements! 🚀

Hello FileNet community,

I would like to hear from you on the content retrieval latency and any known limitations(if any) for the containerized CPE deployed on AWS and using S3 storage as the storage area.

1) Is S3 standard's retrieval performance satisfactory for high ingestion and retrieval requirements?

2) Is there a noticeable latency delay for the documents retrieved from S3 Glacier Instant retrieval storage when compared to S3 standard?

3) Any limitations or issues at CPE end when using S3 lifecycle policy to switch the content from S3 standard to S3 Glacier Instant retrieval storage?

Your input is highly appreciated!