There are a number of factors that contribute to performance aspects of Teradata Viewpoint and enough to warrant an article on this subject. So if you are looking for improved Viewpoint responsiveness and snappier portlet refreshes, consider the aspects covered in this article.

The first thing to consider is that Teradata Viewpoint has several different factors that contribute to performance. Each one of the following factors will be discussed in terms of how it plays into this. The browser, client and dashboard aspects are crucial to a successful self-service deployment because if performance is lacking, usage will follow. Here are the considerations put in order of the extent users can control them.

  • Viewpoint Dashboards
  • Browser
  • Viewpoint Version
  • Client Workstation
  • Network
  • Viewpoint Backup
  • Viewpoint Server

Viewpoint Dashboards

How one populates their Viewpoint dashboards will contribute to the user's Viewpoint experience. Viewpoint's customization capability is of great value in allowing users to set up their experience to exactly what they want and need. However this can work against users too.

All portlets have a similar load time when they are alone on a page. However when there are several portlets on a page, high-impact portlets slow the load time more than low-impact portlets. Browser selection plays into this as well. So the general recommendation is to consider another dashboard page versus over populating a single dashboard. If you are experiencing performance issues, try limiting your pages to 2-3 portlets, having more than four is of little value anyways as it requires scrolling to see them.

Regarding portlet impact, portlets in the medium-impact and high-impact classes run time-consuming queries to collect their data and therefore need to be considered when defining a dashboard. Isolating higher impact portlets to their own dashboard will improve the overall experience.

Low Impact Portlets: My Queries, Remote Console, SQL Scratchpad, System Health, and Todays Statistics. Query Monitor and Query Spotlight also fall into this category unless a very large number of queries are being displayed.

Medium Impact Portlets: Alert Viewer, Calendar, Canary Response Times, Lock Viewer, Metrics Analysis, Node Resources, Productivity, Space Usage, Viewpoint Monitoring, and Workload Health.

High Impact Portlets: Capacity Heatmap, Metrics Graph, Workload Designer, and Workload Monitor.

So keep those trend reporting and workload management dashboards separated from general usage and monitoring dashboards. Note that dashboard configuration will be an important consideration for shareable pages/dashboards planned with Viewpoint 13.12 release. This allows a default dashboard concept for each Viewpoint role. This will allow DBAs more control and influence over users' initial experience with Viewpoint.


Teradata Viewpoint currently supports the following browsers: Firefox 3.6 and Internet Explorer 6.x, 7.x, 8.x. Note that IE 8.x native support was released with Viewpoint 13.11 so earlier Viewpoint versions will require IE 8.x to be run in IE 7.x compatibility mode.

The best performance is going to be realized with the latest browser technologies as these newer versions are optimized for ever changing and maturing industry technologies. The vendors agree. If you go to Microsoft's home page for IE6, the opening information is "It's time to upgrade to the world's most widely-used browser" referring to IE8. Certainly this is part marketing but also an obvious technical recommendation.

In particular, you want a browser that is optimized for Java script applications. A fact that works against IE6 and its release date of August 2001. So if you are using IE6, you need to consider a newer browser even if that means having two browsers installed on your workstation in the event that IE6 is still a standard within your company. Even with all the extra performance code that Viewpoint engineering has implemented for IE6, it still doesn't perform like newer browsers.

This also contributed to the business decision to drop support for IE6 with the Viewpoint 13.12 release following the direction of the internet community. The good news is that at this same time, the plan is to add Firefox 4.x, Chrome, and Safari to the formally supported list.

Viewpoint Version

With each Viewpoint release, there is new code fixing issues, improving performance, and of course providing valuable new features. So keep your Viewpoint version to the latest release. Teradata realizes that four Viewpoint releases in 2010 made that a challenge so going forward, the target will be two Viewpoint releases a year. This strategy is also recommended as a best practices support policy.

Client Workstation

The client workstation considerations are covered in the Teradata Viewpoint Configuration Guide but can be missed by the general Viewpoint community for those not involved with actual Viewpoint configuration aspects. So hopefully this article will reach a greater portion of the Viewpoint community. Note that Teradata Viewpoint is a client/server architecture with dependencies on client workstation performance. If you have old PC or laptop technology, your performance will unfortunately suffer. The current client workstation recommendations are:

  • At least 1.8GHz Pentium M, 3GHz Pentium 4, or equivalent CPU
  • At least 1 GB of memory (RAM)
  • At least 1024x768 resolution for display


Customer's networking and security implementations need to be mentioned as there has been situations where this was a primary cause of performance degradation. So please ensure DNS (Domain Name Services) is properly configured, network performance to Viewpoint and Teradata systems is performing as expected, and that there are no network firewall limitations to http access. Don't forget the remote aspects, so ensure that VPN access to Viewpoint performs similarly to in-office/Intranet access so remote users get a positive experience too.

Viewpoint Backup

Schedule the automated Viewpoint DCS backup at a time when Viewpoint usage is expected to be low. The Viewpoint Admin screen shot below may not be optimal.


Viewpoint Server

Obviously, the Viewpoint server itself is part of the performance considerations, and in particular when monitoring multiples of high activity Teradata systems. Suggest using the "Viewpoint Monitoring" portlet to check server resources like I/O and CPU to ensure the Viewpoint instance is not saturated.


If Viewpoint does appear saturated, then resolution considerations may be moving some Teradata Systems to another server, tuning data collection frequency, or potentially acquiring a higher performance Viewpoint server. This would warrant an incident submission to Teradata Global Support for analysis and recommendation.

Related to this is to also ensure the data collection repository (DCS) is not nearing full capacity. This can be verified in the Admin menus under "Teradata Systems" and "Disk usage" as shown below.

If the DCS is nearing capacity, then adjustments to data retention should be considered. By drilling into the blocks on this display, one can see each data collector and the amount of space each is consuming. Another drill down then allows easy adjust of that particular data collector's collection and/or retention rates.

Note there have been three generations of Viewpoint servers. The most recent two, models 415 and 617, should have plenty of horsepower. The initial Viewpoint server release had less processing power so something to consider.

So there are some recommendations for performance considerations of the Teradata Viewpoint implementation.

Hope this helps.

SeanM 3 comments Joined 04/11
27 Apr 2011

Hey Gary,
Are there any recommendations or considerations on the number of concurrent users a Viewpoint instance can support?

Apologies if you answered this on another article or thread. Was not able to find it.

gryback 151 comments Joined 12/08
28 Apr 2011

It was not mentioned in this article but was in the discussion regarding the need for additional Viewpoint instances. That link is below but in short, we target 350 concurrent users as threshold where another Viewpoint server may be needed but it depends also on usage patterns and how many Teradata systems are being monitored. Here's that URL:

gryback 151 comments Joined 12/08
10 May 2011

Has this article assisted anyone out there with improved performance? Interested in sharing of stories where others may benefit.

jf185051 1 comment Joined 07/10
13 May 2011

This is a useful article yes. I have a few recommendations that experience has shown also impacts Viewpoint performance that might be good to include.

Space on the Linux slices - If Viewpoint is performing slow you can use an secure shell client, putty for example, to connect to the Viewpoint operating environment (SLES) and run the "df" command to see how much space is left on the slices. If any of them are higher than 90% it may be good to see what is filling the slice up. Sometimes there are abnormally high number of dcs backups being kept on the Viewpoint server. Just to give one example.

Number of Teradata Systems being monitored - If the number and size of the Teradata systems being monitored on a single instance of Viewpoint is exceeding a practical threshold this can impact Viewpoint's responsiveness.

Errors on the DCS collectors - It's a good idea to verify that you don't have a lot of dcs collectors that are failing for some reason. Check the stack traces for the errors in Admin -> Teradata Systems and correct them or disable the failing collector until it can be corrected.

Multi-System Manager client package version - If the Viewpoint server is being used to view the TMSM portlets it will have the tmsm publisher packages and services installed. You want to make sure you have at least the 13.10 tmsm client packages. There was heap usage cap put on the publisher at this version to prevent it from consuming too much memory. You can check for the package version with "rpm -qa | grep tmsm".

I hope this helps.

gryback 151 comments Joined 12/08
13 May 2011

Thanks for the feedback. Note that with the next Viewpoint release (13.12), you will be able to create alerts for the DCS collectors for easy notification, like email, if there is an issue with them. That should help in the management aspects of Viewpoint.

AbeK 37 comments Joined 08/09
13 May 2011

This certainly is very useful and help me configure the data retention for the different collectors, appropriately. Also helped in identifying the IO issues with the IO subsystem for the Postgresql database.
Thanks for your guidance.

Glass 3 comments Joined 04/10
15 Jul 2011

When editing, then activating a new ruleset in Workload Designer portlet I frequently get an error after 2-3 minutes of working that an error has been encountered activating the request. If I close the page and return a few minutes later the ruleset has been activated.

While the system is under essentially the same workload, I can use Workload Management in TDmanager and change the same workload in about 5 seconds with no errors.

Should I be getting similar response time in Viewpoint, or can I expect this operation to always take much longer?

Robert Glass

gryback 151 comments Joined 12/08
15 Jul 2011


Your posting is probably more appropriate for a forum posting than attached to a somewhat unrelated article. It also may warrant a GSC incident but here's some information anyways.

The activation should take the same the amount of time from either Viewpoint's Workload Designer as TDWM. However in Viewpoint three is two operations, a "make ready" and "activate". If you do an activate without a make ready, it does both behind the scenes and may result in a longer duration than Teradata Manager due to the different architectures.

You shouldn't be seeing errors regardless, so you should submit an incident on that as there could be something else unexpected occurring.

geethareddy 145 comments Joined 10/11
14 Dec 2011

hi Gary,

We have 13.11 VP on one of the business lines. Now a days a set of users who are using client machines on (WINDOWS 7) are experiecing a significant amount of delay. Just to bring up the log in page it is taking >5 mints. Again for each click on any portlets its taking same amount of delay, we raised an incident to Teradata. They referred to your performance considerations article :) at ( But there I didnt find any of the aspects are causing the delay on WINDOWS 7 machine. I strongly believe WINDOWS 7 release it self a resource consuming among all Microsoft windows versions. Did you hear anything specific issues with WINDOWs 7 with any other client OR you want me to check any thing else with this issue.


gryback 151 comments Joined 12/08
14 Dec 2011

I have not heard of any general issues with Windows 7 and usage of Viewpoint. I would go back to the incident owners and escalate stating that nothing in the performance article seems to apply and further investigation is warranted.

qbuck 3 comments Joined 02/12
07 Mar 2012

Hi All,
We have 13.12 VP and when we click Make Ready on Our Ruleset, there's a warning message "The version cannot be null". Anybody knows you know what caused this?


gryback 151 comments Joined 12/08
07 Mar 2012


This type of question would be more appropriate as a Viewpoint forum post than a comment to a somewhat unrelated article. Or better yet, you may just want to create a GSC support incident.


Nageswara Rao 1 comment Joined 04/12
12 Apr 2012


I am using VP to run the quires ... Can you please let me know if any option to export result in VP.

geethareddy 145 comments Joined 10/11
12 Apr 2012

Are you using SQL Scratch pad? If you are using it, yes you can export results after executing the queries.



gryback 151 comments Joined 12/08
13 Apr 2012

There is an export option in SQL Scratchpad as well as Query Monitor both of which export information out to a CSV file format. If you are not seeing those options, you may need to upgrade your Viewpoint version.

gsoh 14 comments Joined 08/12
20 Aug 2012

Hi, When I check the DBC.Qrylog data, I was found some issue about viewpoint user collecting log to DBQL.
Too many viewpoint data storing the DBQL tables, How can i reducing this Log data at DBQL.

gryback 151 comments Joined 12/08
20 Aug 2012

Is your concern that the Viewpoint login and queries are numerous in DBQL?

gsoh 14 comments Joined 08/12
06 Sep 2012

Yes, we was setting DBQL with all users, after we was checked the DBQL login count by each user, But VP user was Many rows inserted the DBQL. We'll changing the DBQL setting except Viewpoint, But Why

gryback 151 comments Joined 12/08
10 Sep 2012

That would be expected. The "viewpoint" user is logging into Teradata to run SQL for some levels of data collection. So one would expect to see Viewpoint in DBQL if logging was enabled for all users.

You must sign in to leave a comment.