Skip to Content
0
May 12, 2015 at 02:33 PM

Soft state implementation considerations

351 Views

Hello,

I am going through Soft State Support for OData Services - SAP NetWeaver Gateway - SAP Library and there come across implementation consideration section. I need more information on few points such as,

  • Resources on the server stay occupied as long as the application server session lives. It means that the more services run in soft state mode the more server resources are constantly unavailable. The price you pay for better performance is a higher memory consumption, hence:
  • The soft state timeout should be short.
  • Soft state should only be used in special situations, that is, only for certain entity sets.

1) is there any guideline on what should be the soft state timeout value depending on number of concurrent users (for e.g. 500 to 1000 users)? what other parameters one need to consider while determining soft state timeout value?

2) Soft state should only be used in special situations, that is, only for certain entity sets - soft state feature applies to entire OData service. what is meant by certain entity sets? or I am missing something.

3) Should we consider soft state support for implementing lock mechanism as being discussed in few discussions such as and Or this feature should be specifically used for improving performance by caching data as mentioned by Andre Fischer in the post How to use Soft-State support for OData services

By using soft state, the resources/functionality which has been loaded during the initial load can be reused for the subsequent requests of the service. Thus, the main benefit of soft state is a considerable performance optimization of an OData service.

Regards,

Chandra