Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Since the Billing Preview is a “Preview”, what changes can I expect by the time actual billing begins for Windows Azure platform AppFabric?

0
Posted

Since the Billing Preview is a “Preview”, what changes can I expect by the time actual billing begins for Windows Azure platform AppFabric?

0

The following issues exist in the AppFabric Billing Preview and will be fixed or addressed before the start of billing: 1) Message Buffers are underreported in some scenarios: instead of counting at least one connection for the lifetime of each message buffer, no connection is reported when there is no listener on the message buffer. 2) Connection count is underreported for short-lived connections: some of the processing time for a connection is not considered when determining the number of concurrent connections, which can result in underreporting of connections of up to 50% in some scenarios. 3) Default connection pool timeout for NetTcp-based protocols in the AppFabric SDK is 2 minutes: this can result in a higher than expected connection count in some scenarios. A workaround is to explicitly configure the connection pool timeout via application configuration (at the cost of some performance for clients that do relatively frequent reconnects within the timeout period). We are lookin

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123