Hi,

I posted a comment here --> http://www.imiscommunity.com/imis_15_0_15_1_15_2_performance_degredation#comment-13129

But in case that thread is dead, I'm trying to setup iMIS so that when application pool recycles, users do not loose their session.

From other posts, I've seen recommendation to set machinekey to a statickey and then when application pool recycles, session state won't be lost for the user.

Our iMIS users (staff and members) cannot log in after the IIS app pool automatically recycles on our produciton iMIS installation. Once we manually recycle the application pool, the problem clears up.

The specifc error message on browsing the app server website (i.e. http://server-url/imis15) is: "Document not found or insufficient permissions to read document. $/Business Object Schema/User"

When running iMIS15 Desktop, the program opens correctly but when doing a Find, it takes close to five minutes to open a record.  Has anyone else experienced this issue running iMIS15 from an image?

 -Katie

Katie Miller
kmiller@naifa.org

Symptom: If you're seeing random, periodic extremely slow page refreshes on your iMIS app server (full or public view, either one), check the first section of this Howto for the ASP.Net "idle worker process timeout" setting.

The issue is that by default, IIS kills the ASP.Net worker process after 20 minutes of inactivity, causing the next page access to restart the appdomain (leading to that annoying "first hit" slowdown as all the business objects are loaded, iBO initialized, etc).

Hi all,

I was wondering if there is an option to enable E-mail redirecting to a single account to prevent Customers in the database from receiving test E-mails?

Thanks.

We are currently using the iMIS 15 public website and are experiencing bad performance. Upon viewing the source it was noticed that the system calls +/- 31 stylesheets on each page.

We have updated the styles and themes as much as possible so that the site looks in line with the Clients CI but because of all these stylesheet calls the site is extremely slow and unresponsive at times.

We have done some .Net integration into the iMIS database and these pages are almost instantanious...

In the days of client/server applications the amount of data sent “over the wire” was not typically a huge concern unless the data was very big. This is because client/server applications typically run on local networks with 10, 100 or even 1000 Mbps connections; plenty of speed for most data applications. In the web world, however, more people access their application over remote networks, like from remote offices, home, or Starbucks. These are typically much slower connections, have to go thru many routers along the way (called “hops”), and often travel thru VPNs which encrypt/decrypt the data along the way.

I came accross this article, which goes into one of the major software design misconceptions out there. I've heard this echoed many times: XML doesn't have to be compact, the network will get faster; Java doesn't have to be fast computers will get faster, etc.

I've also seen many systems bogged down with fundamental designs enforcing poor performance. Most of the time the problem is designers that don't understand the impact of shared resources on a web server. They worry about CPU cycles on individual requests when they use a property heavy remote object, or abuse a database with multiple small requests in a transaction.

I was recently asked to provide some guidelines or practical feedback on how to get the most performance out of e-CM as possible. First of all, e-CM has gone through many changes and performance enhancements over the years. It has been well optimized for performance.

That being said the following are 3 main things (from least to most important) that someone setting up e-CM can do to maximize its performance: