2013.2 Performance

Question

I've been getting reports that the performance of 2013.2 is slower than the previous version of ADAxes.

Searching, editing, etc.

Is this a known issue?

Comments

Hello,

What version (including the build number) are you using? Are Adaxes service and Adaxes Web Interface installed on the same computer or different computers? Are they in the same AD site? Please describe your environment in more detail.

Also, can you draw up at least an approximate list of pages that load slow?

---

Version 3.6.10022.0 (64 bit)

Running on a single server. 8.00 GB RAM.

It is a virtual server running in VMWare ESX 4.1

Results from searches seems to be the biggest complaint.

---

Just a qucik tip that we have experienced (if this is regarding the web interface). Google Chrome works MUCH quicker with the Adaxes Web Interface then IE. We were struggeling with slow performance, tried rebuilding everything, same problems.. Then someone tried it through Google Chrome, super quick response!

---

Hello,

Can you do the following:

1. Enable tracing in Adaxes Web Interface (see instructions below).
2. Try opening some pages that load slow.
3. With tracing enabled, the pages will have some tracing information at the bottom. Save the pages as HTML files and send them to our support e-mail (support[at]adaxes.com).

To enable tracing in the Web Interface:

1. Open the folder that contains the Web Interface site that you are experiencing issues with. By default, Adaxes Web Interface sites are installed to the following folders:
   Administrators:
   C:\Program Files\Softerra\Adaxes 3\Web Interface\Admin\
   Help Desk:
   C:\Program Files\Softerra\Adaxes 3\Web Interface\HelpDesk\
   Self-Service:
   C:\Program Files\Softerra\Adaxes 3\Web Interface\SelfService\

2. Find the Web.config file and open it with any text editor.

3. Find the following lines in the file:

    <!--- Trace settings -->
    <trace enabled="false" pageOutput="true" requestLimit="40" localOnly="false" mostRecent="true" />
   

4. Change trace enabled="false" to trace enabled="true".

5. Find the following lines:

    <!-- Web settings -->
    <system.web>
   

6. Paste the following block before the lines:

    <system.diagnostics>
      <trace>
        <listeners>
           <add name="WebPageTraceListener" 
                type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
        </listeners>
      </trace>
    </system.diagnostics>
   

7. Save the file.

---

Thank you for the information.

I've not changed anything at this point. We do use Chrome and I find the performance the same as it has always been (fast).

Sometimes, information gets lost in translation.