Overview

 The following MVP performance issues may be observed:

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

Suggested Fixes

The proper remedy recommendation is based on two possible scenarios:

1. A high number of nesting or real-time device monitoring folders.
2. A high number of individual third-party devices or large printer fleet.

1. Folder Structure Remedy

Fix

Increase memory allocation limits on MVP server and client machines. Click here for for further instructions on how to increase this value.

Why? 

Memory utilization is dependent upon the total number of nesting folders, and the number of folders designed to monitor "errors", "warnings" or "intervention requested" type messages.

MVP Behavior

First, when MVP filters devices into folders, it validates each device against all the folders on the server(s).

An increase in filtering and folder creation results in a steady accumulation of nested folders and an increase in the number validations. This increase in the number of validations creates a need for greater memory requirements. 

Second, the real-time (live) monitoring of device status over a MVP/network communication channel requires increased memory resources. However, MVP uses only a single thread to listen to status changes on monitored devices for these folder types. 

2. Third-Party Device and Large Printer Fleets Remedy

Fix

Adjust polling rate or status ping intervals. 

To do this:

1. Open MVP.
2. Click on MarkVision.
3. Click on Administrative Settings.
4. Click on Intervals.
5. Change polling rate to 60 minutes.
6. Increase status ping intervals to 30-60 minutes.

Click here for screen shot of this location. 

Why?

Monitoring "status" changes on third-party devices or testing communication status on large fleets creates performance challenges.

MVP "Polling rate" Behavior

If you are monitoring any change in printer "status" of a third-party device, each new folder created for this purpose creates one new thread for each third-party device. This causes high memory usage, and depending on the number of third-party devices on the server, the server may become very slow or unresponsive.

MVP "Status ping" Behavior

Status ping determines the communicating status of devices on the server. Very low values cause MVP to become too busy polling devices.

For example, a status ping setting of 1 minute with a server containing ~500 devices would cause the server to be very busy and impact performance of other assigned tasks.

Still Need Help?

If you require additional assistance, please see Contact Lexmark information. NOTE: When calling for phone support, you will need your model/machine type and serial number (SN).

For improved technical support, all callers should be near the computer and the printer in case the technician on the phone asks you to perform a task involving one of the devices.