Thank you for your feedback



MarkVision Professional 11.1 and 11.2 Performance Improvement and Upgrade Tips (06-2010)

Document ID:HO3640
 
  Properties  

Problem

Server crash; Server freeze; Performance tips; MVP server becomes slow; High memory usage; Unexpected system; Application crashes; Devices disappearing from the server; MVP 11.1 server performance; Markvision professional issues

Solution

Overview

 

 The following MVP 11.1 performance issues may be observed in an environment where MVP server has a considerable amount of folders and action alerts:

  • - The MVP server becomes slow or unresponsive
  • - High memory usage is seen on the server or client
  • - Unexpected system or application crashes or the server freezes 

 


Recommended Action

Update to Markvision Professional 11.2.1 and perform the necessary system optimizations found in this article.

 

 

In this article

The following should be followed in this order if considering the upgrade to the MVP 11.2.1:

  1. Make a backup copy of the data folder
  2. Uninstall Markvision Professional 11.1 and Install MVP 11.2.1
  3. Application settings and Performance Optimization with Available Plug-ins
  4. Folder Structure, Performance Effects and Other Recommendations

 

 

 

 

 

Step 1: Make a backup copy the MVP 11.1 "granite" directory

 

Click here for instructions if you need additional assistance.

 

 

 

 

Step 2:  Uninstall Markvision 11.1 and Install MVP 11.2.1

 

Uninstall the application using the Lexmark Software Uninstall found within Add or Remove programs. Afterward, install the MVP 11.2.1 application on the same PC.

 

 

 

 

Step 3: Application settings and Performance Optimization with Available Plug-ins

 

The following optimization steps will further increase performance behavior:

  • - Increase MVP server resources
  • - Install additional Plug-ins
  • - Change polling or status intervals
  • - Change element persistence value

 

Increase MVP server resources

On completion of the installation and the system restart go to the registry editor and set the memory at Lexmark > MarkVision server\Granite\1.0 > JVM_Options to:

"-ms256M -mx1536M" or higher

NOTE: Recommended 2048M if more memory is available.


  And, adjust the the registry value for Lexmark > MarkVision for intranets to:

"-ms512M -mx1024M -Duser.language=en."

 Click here for additional assistance. 

 

Install Additional Plug-ins

Plug-in Plug-in Function
1.Click here  to download. Helps handle the case of too may threads being initiated by MVP while handling third party devices.
2. Click here to download. Helps handle the issue of devices disappearing from the server after a server restart.
3. Click here to download. Helps clear out memory on the MVP server at each status ping interval.

Click here for additional information on how to install Plug-ins.

 


Adjust polling rate or status ping intervals. 

 

To do this:

  1. Stop the server.
  2. Copy the backed up data folder from Step 1 to the newly created granite directory after the 11.2.1 install.
  3. Start the server.
  4. Open MVP.
  5. Click on MarkVision.
  6. Click on Administrative Settings.
  7. Click on Intervals.
  8. Change polling rate to 60 minutes. Especially recommended for multi-vendor environments. 
  9. Increase status ping intervals to 30-60 minutes.

Click here for screen shot of this location.

 

 

 

Change the time interval for persistent data to be written (element persistence value)

  1. Go to the server web page at http://localhost:9180/~MvServer and click on the "Parameters" tab.
  2. Lookup for the parameter called "services.persistence.elementPersist".
  3. Set the value to 1200, wait for 10 minutes and then restart MVserver. (This is to make sure that the settings changes take effect on the server).

Click here for additional information on how to change this value.

 

 

 

 

 

Step 4: Folder Structure, Performance Effects, and Other Recommendations

 

 

Administrators that opt to perform daily scheduled discoveries with servers that host several existing nested folders, and alert related folders, will experience the memory intensive nature of this type of configuration and the resource burden it will place on the server. 

Performance scenario

To help understand the cumulative or aggregate effect on server resources, imagine the following: 

  • - A newly discovered device is being filtered through multitudes of folders, and validated against each folder structure, before being fitted into a suitable place.
  • - Concurrently, several devices on several different subnets are being validated with alert-based folders e.g. paper jam,supply low/empty etc.
  • - In response, MVP receives the state changes on the devices and accordingly refreshes its data.
  • - One last simultaneous refresh is initiated by MVP for validation between device and alert (folder/filter structure) to confirm status. 

 

Performance decisions 

  • - Decide whether or not to share the load between two or more servers based on the above scenario; this configuration would require identical settings on each server.  
  • - Understand that user configuration methods can greatly impact performance.

 

Other Performance recommendations

  1. If possible, do not run the discovery daily and schedule discovery intervals to every 3 days or a week. 
  2. If possible, restart of the server once or twice a month.  

 

 

 

Still Need Help?

Please contact Lexmark if you need additional support assistance. NOTE: When calling for support, you will be asked for your MFP machine/model type and serial number (SN).


Please call from near a computer and printer in case the technician on the phone asks you to perform a task involving one or all of these devices

 



Link:
Please enter the email address you would like to send a copy of this page to.