Bad performance: Xpath View causes database server almost 100% cpu

Hi there,
Since I am rather inexperienced in using the Oracle XML DB I wonder If I am doing wrong with the following:
I created a table with a xmltype column in it:
CREATE TABLE LPD_LOAD_XML
FILENAME VARCHAR2(50 BYTE) NOT NULL,
XML_CONTENT SYS.XMLTYPE,
DATE_CREATED DATE DEFAULT sysdate NOT NULL,
CREATED_BY VARCHAR2(30 BYTE) DEFAULT user NOT NULL
and I am using a xpath query to retrieve the data which is stored in the xmltype column:
select extractvalue(value(p),'/medobj@barcode') barcode
, extractvalue(value(p),'/medobj@VJ') vj
, extractvalue(value(p),'/medobj@FNF') fnf
, extractvalue(value(p),'/medobj@GLB') glb
, cast ( multiset ( select extractvalue(value(q),'/author@cap') cap
, extractvalue(value(q),'/author/name/addpre') addpre
, extractvalue(value(q),'/author/name/fname') fname
, extractvalue(value(q),'/author/name/prefix') prefix
, extractvalue(value(q),'/author/name/lname') lname
, extractvalue(value(q),'/author/name/addapp') addapp
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/author'))) q
) as authors_type_nst
) as authors_type
, cursor(select extractvalue(value(q),'/corp.author') corp_author
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/corp.author'))) q
, extractvalue(value(p),'/medobj/isbd/auti') auti
, extractvalue(value(p),'/medobj/isbd/edition') edition
, cursor(select extractvalue(value(q),'/impressum/pofpublication') pofpublication
, extractvalue(value(q),'/impressum/publisher') publisher
, extractvalue(value(q),'/impressum/pyr') pyr
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/isbd/impressum'))) q
, extractvalue(value(p),'/medobj/isbd/collation/extent') extent
, extractvalue(value(p),'/medobj/isbd/collation/illustration') illustration
, extractvalue(value(p),'/medobj/isbd/collation/size') size_
, extractvalue(value(p),'/medobj/isbd/collation/enclosure') enclosure
, cursor(select extractvalue(value(q),'/series/series.title') series_title
, extractvalue(value(q),'/series/series.nr') series_nr
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/isbd/series'))) q
, extractvalue(value(p),'/medobj/isbd/part') part
, extractvalue(value(p),'/medobj/isbd/annotation') annotation
, extractvalue(value(p),'/medobj/isbdblock') isdbblock
, extractvalue(value(p),'/medobj/isbn/t') isbn_t
, extractvalue(value(p),'/medobj/isbn/d') isbn_d
, extractvalue(value(p),'/medobj/isbn/uh') isbn_uh
, cursor(select extractvalue(value(q),'/isbn2/t') isbn2_t
, extractvalue(value(q),'/isbn2/d') isbn2_d
, extractvalue(value(q),'/isbn2/uh') isbn2_uh
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/isbn2'))) q
, cursor(select extractvalue(value(q),'/label') label
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/label'))) q
, extractvalue(value(p),'/medobj/ppn') ppn
, cursor(select extractvalue(value(q),'/note') note
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/note'))) q
, extractvalue(value(p),'/medobj/sysreq') sysreq
, extractvalue(value(p),'/medobj/mat') mat
, extractvalue(value(p),'/medobj/lang.content') lang_content
, cursor(select extractvalue(value(q),'/siso@type') siso_type
, extractvalue(value(q),'/siso@rank') siso_rank
, extractvalue(value(q),'/siso') siso
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/siso'))) q
, cursor(select extractvalue(value(q),'/subject@rank') rank
, extractvalue(value(q),'/subject') subject
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/subjectheading/subject'))) q
, cursor(select extractvalue(value(q),'/genre/genre.full') genre_full
, extractvalue(value(q),'/genre/genre.abbr') genre_abbr
, extractvalue(value(q),'/genre/genre.cd') genre_cd
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/genre'))) q
, extractvalue(value(p),'/medobj/agecat') agecat
, extractvalue(value(p),'/medobj/readinglevel') readinglevel
, extractvalue(value(p),'/medobj/avi') avi
, extractvalue(value(p),'/medobj/review') review
, extractvalue(value(p),'/medobj/reviewer') reviewer
, cursor(select extractvalue(value(q),'/cover') cover
from TABLE(xmlsequence(EXTRACT(value(p),'medobj/cover'))) q
from lpd_load_xml i
, TABLE(xmlsequence(EXTRACT(i.xml_content,'bmo/medobj'))) p
where i.filename = b_FileName
You can see that I am using both CAST MULTISET and a cursor, since I am finding out the best way. I have to use either one because the xml is stored in a hierarchical way. But now i am lost. What is most surprising to me is that the database server is really 100% dedicated in mastering this query. Is there anyway to avoid this? How can I retrieve the data in the xml file from within the database without causing a slow performance?
Greets,
William de Ronde

Have you created indexes on the XMLtype Column? Either way, if i am not mistaken then your XMLType column will default to XMLType CLOB storage. This will cause that your XML data will be put completly into memory regarding the inbetween resultsets. Use dmbs_xplan procedure, autotrace on (in sqlplus) or tkprof tools to find out whats happening. Did you generate statistics on your table via DBMS_GATHER_STATS package (don't use the analyze statment) ?

Similar Messages

Fontd and PS take me almost 100% CPU

When I am using font function in Photoshop, fontd and PS take me almost 100% CPU!!
How can i solve this?

Captain Ibuprofen, we actually continued having the slowness problem in the past week. Then one of our developers found out the reason: as same as yours, caused by the page number widget. I wish we would have seen your response earlier. But yeah, so now we took out the page number widget and everything goes normal.
Also thanks for the tips on using the cpInfoCurrentSlide variable when adding the slide number. Thanks Andy.

Firefox using almost 100% CPU - hogging resources - hanging

After several hours of operating Firefox starts using almost 100% CPU - with peaks of 100% occurring in rapid succession - FF hangs until CPU useage drops below 100%
Followed recommended troubleshooting as recommended on this site:
* Started in Safe mode - no problems occurred.
* Disabled all extensions; Plug-ins left operating.
* No replication of problems.
* Enable 1/2 of extensions up to Flashblock - restarted - seems ok
* Enable most remaining extensions
* (There are 3 Java extesnions - only enabling one) - again seems ok
* Some hours later - problem reoccurred. Each time CPU useage peaked at 100% (according to Task Manager) the Firefox Window flickered & was unresponsive.
* Deleted cache - no change
* Disabled recently added programs - no change
FF opens and closes normally & completely. '''Problem only seems to occur after FF has been operating for some time'''
This has occurred intermittantly before but has become chronic over the last few days. Apologies if I've been repetitive or explained poorly - FF has hung several times while typing this.

No issue for me, after 4 loops my CPU load was around 18%.
Firefox 33.1.1 under Windows Vista.

After starting up the listener the server consuming 100% CPU

Hi,
when i startup the database tier (EBS 12.1.3 and DB 11.2.0.2) its stared well and the CPU usage is normal.But when i start the listener the server (RHEL 5.8) start consuming 100% CPU.
alert.log details
in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j000_7601.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:11:33 2012
Sweep [inc][480592]: completed
Wed Dec 12 10:13:17 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc (incident=480612):
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:13:18 2012
Sweep [inc][480612]: completed
Wed Dec 12 10:14:18 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_ora_7814.trc (incident=481092):
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/incident/incdir_481092/UAT_ora_7814_i481092.trc
Wed Dec 12 10:14:23 2012
Dumping diagnostic data in directory=[cdmp_20121212101423], requested by (instance=1, osid=7814), summary=[incident=481092].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Dec 12 10:14:24 2012
Sweep [inc][481092]: completed
Sweep [inc2][481092]: completed
Wed Dec 12 10:16:50 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc (incident=481492):
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:19:04 2012
Incremental checkpoint up to RBA [0xf.ac257.0], current log tail at RBA [0xf.c3691.0]
Wed Dec 12 10:20:56 2012
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of ASHSIZE to a sufficiently large value. Currently, ASH size is 2097152 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
select total_size,awr_flush_emergency_count from v$ash_info;
Wed Dec 12 10:21:26 2012
Sweep [inc][481492]: completed

Please see these docs.
ORA-600/ORA-7445/ORA-700 Error Look-up Tool [ID 153788.1]
ORA-600 [13011] "Problem occurred when trying to delete a row" [ID 28184.1]
Workflow Control Queue Clean Up Program Fails With ORA-25226 [ID 334237.1]
Thanks,
Hussein

Bad performance when using complex database view with Toplink

Hi
Problem description
1. I have a complex query that collects the data from many DB tables. For this reason I create a database view based on this select. Using EJB 3.0 with Toplink I
mapped this view to a java object the same way I map database tables. The method I use to get the results is:
snippet code...
public List<VwKartela> VwKartela(Integer pperid) {
List<VwKartela> results = null;
Session session = getSessionFactory().acquireSession();
ExpressionBuilder bankfile = new ExpressionBuilder();
Expression exp1 = bankfile.get("perid").equal(pperid);
ReadAllQuery query = new ReadAllQuery();
query.setReferenceClass(VwKartela.class);
query.setSelectionCriteria(exp1);
results =(List<VwKartela>)session.executeQuery(query);
When running the select on the view prom SQL Plus I haven’t any performance problem.
2.Question: How can I improve the performance? I referenced to Toplink docs but I didn't improve the it.
Have anyone any experience is such cases?
Thank you
Thanos

Hi
After my last tests I conclude at the followings:
The query returns 1-30 records
Test 1: Using Form Builder
- Execution time 7-8 seconds
Test 2: Using Jdeveloper/Toplink/EJB 3.0/ADF and Oracle AS 10.1.3.0
- Execution time 25-27 seconds
Test 3: Using JDBC/ADF and Oracle AS 10.1.3.0
- Execution time 17-18 seconds
When I use:
session.setLogLevel(SessionLog.FINE) and
session.setProfiler(new PerformanceProfiler())
I don’t see any improvement in the execution time of the query.
Thank you
Thanos

Please help: Course loads very slow and takes almost 100% cpu and 1.08 GB memory

The total page number is 129. We used Captivate 5.5. We have several Webpage widgets and a few videos. I tried to take out the web widgets and the videos, however, the course still loads very slow.
I would really appreciate if someone can give somve suggestion.
Thank you very much.

Captain Ibuprofen, we actually continued having the slowness problem in the past week. Then one of our developers found out the reason: as same as yours, caused by the page number widget. I wish we would have seen your response earlier. But yeah, so now we took out the page number widget and everything goes normal.
Also thanks for the tips on using the cpInfoCurrentSlide variable when adding the slide number. Thanks Andy.

Performance issue after upgrading database 9i (9.2.0.5.0) to 10g (10.2.5.0)

Hi,
recently we have upraded our database from 9.2.0.5.0 to 10.2.5.0. After the upgrading of the database some of our SQL-statements, who gather data and fill it in an empty tabless,
shows a really bad performance in the new database version. We already have checked the explain plan it remains the same in both versions (full table scans on the corresponding tables)
E.g. a query running in the 9i database needs 17 minutes for completion in the 10g version it needs 15 hours.
We have checked the running session and have seen that the read of database blocks of the corresponding tables needs immense more time in the 10g version.
Are there any oracle parameter, hidden features we can adjust in 10g in order to get the same performance as in 9i?
thanks in advance
Here is this example with the above mentioned different response time:
(the object edv_belasgv_3_jahre is a view over 3 tables as an union all, each table has approximately 1 million records)
/* Formatted on 06.09.2012 19:09:08 (QP5 v5.136.908.31019) */
INSERT INTO mv_edv_belasgv_branche
SELECT gesellschaft,
erscheinungsdatum,
buchungsdatum,
code,
SUM (rechnungsnetto) AS rechnungsnetto,
SUM (rechnungsbetrag) AS rechnungsbetrag,
SUM (mehrwertsteuer) AS mehrwertsteuer
FROM (SELECT gesellschaft,
erscheinungsdatum,
buchungsdatum,
rechnungsnetto,
rechnungsbetrag,
mehrwertsteuer,
DECODE (
(SELECT branche1
FROM anzedv.edv_stammdaten t2
WHERE t1.gesellschaft = t2.gesellschaft
AND t1.kundennummer_sap = t2.kundennummer_sap
AND t1.unterkonto = t2.unterkonto),
NULL,
NULL,
DECODE (
(SELECT DISTINCT branche
FROM (SELECT *
FROM anzedv.edv_zuordnung_branche_rubrik
WHERE branche IS NOT NULL)
WHERE (SELECT branche1
FROM anzedv.edv_stammdaten t2
WHERE t1.gesellschaft = t2.gesellschaft
AND t1.kundennummer_sap =
t2.kundennummer_sap
AND t1.unterkonto = t2.unterkonto) LIKE
branche || '%'),
NULL,
'sonstige',
(SELECT DISTINCT branche
FROM (SELECT *
FROM anzedv.edv_zuordnung_branche_rubrik
WHERE branche IS NOT NULL)
WHERE (SELECT branche1
FROM anzedv.edv_stammdaten t2
WHERE t1.gesellschaft = t2.gesellschaft
AND t1.kundennummer_sap =
t2.kundennummer_sap
AND t1.unterkonto = t2.unterkonto) LIKE
branche || '%')))
AS code
FROM edv_belasgv_3_jahre t1
WHERE gesellschaft IN ('T', 'U')
AND (satzart = 'B'
OR satzart = 'G'
AND gegenkonto_art IN (5000, 5001, 7900)))
GROUP BY gesellschaft,
erscheinungsdatum,
buchungsdatum,
code

There is no 10.2.5.0 version - I assume you mean 10.2.0.5.
Pl see these threads on how to post a tuning request (pl post explain plans from both databases)
When your query takes too long ...
HOW TO: Post a SQL statement tuning request - template posting
Pl also compare the init.ora parameters between the old and new database and post any differences here. Have statistics been gathered on the new database ?
Pl see these MOS Docs
TROUBLESHOOTING: Server Upgrade Results in Slow Query Performance [ID 160089.1]
Query Performance Degradation - Upgrade Related - Recommended Actions [ID 745216.1]
Tips for avoiding upgrade related query problems [ID 167086.1]
HTH
Srini

FMLE CPU almost 100%?

Hi everyone, Please I need help. I use flash media live encoder to livestream at our church and I get almost 100% CPU usage. I dont have any other programs running just flash media live encoder and as soon as i press to start streaming, CPU usages jumps all the way up.
Below is my equipment I use
AMD Athlon II X4 640 Quad Core 3.0GHz CPU
MSI 970A-G46 AM3+ AMD 970 + SB950 Motherboard
G.SKILL Ripjaws Series 8GB 240-Pin DDR3 SDRAM DDR3 1600 RAM
EVGA 02G-P4-3658-KR GeFrce GTX 650 Ti 2GB 192-bit GDDR5 Video Card
Windows 7 Ultimate x64 OS
So I have 3 cameras I use and those cameras go into my ATEM TVS via HDMI or SDI. from ATEM TVS it goes to a PCI capture card. I've tried using
Blackmagic Design Intensity Pro
AVERMEDIA Game Broadcaster HD
AVerMedia Game Recorder -C985
All Three of these capture cards (same result)
I want to be able to stream HD quality 720-1080p at least that is what my streaming provider is telling me I should be able to do. so my settings are as follows. input is 1920 by 1080. output is 1280 by 720. Pretty reasonable. No matter what card I choose my settings are for H265 30fps I've tried all types of frames. and tried all times of bit rates. from 150 to 2000 kbps. always running at very high CPU. Please help me out. Thanks all

I Remember, that was a problem with 100% CPU for 10.1, 10.2 database by LISTENER
Need to rename $ORACLE_HOME/opmn/ons.conf to something else.
and restart listener.
It's may be useful if you installed OEM with database on the same server. Or problem can be anywhere else.

DI job causing high levels of I/O on database server

We have a DI job that is loading a sql server 2005 database. When the facts are loaded itu2019s causingu2019s a high level of I/O on the database server causing the DI job to slow down. No more than 5 facts are loaded concurrently. The fact dataflows all have a sql transform to run the select query against the DB, a few query transforms to do lookups to get dimension keys, and all do inserts to the target. The DBA says there are too many DB connections open and DI is not closing them. My thinking was DI would manage the open connections for lookup, etc and would close then properly when the dataflow is complete.
Any thoughts on what else would cause high levels of DB I/O?
Additional Info:
- Run the DI job, source and target tables are in SQL Server, and it takes 5 hours.
- Run the same DI job again, on the same data set, and it takes 12+ hours. This run will have high levels on DB I/O.
- But if SQL Server is stopped and restart, the job will again take 5 hours the first time it runs.
Edited by: Chris Sam on Apr 15, 2009 3:43 PM

There are a lot of areas of a DI Job that can be tuned for performance, but given the fact that your job runs fine after the database is restarted, it sounds like a problem with the database server and not the Data Integrator job.
There are a lot of resources out there for dealing with SQL Server disk IO bottlenecks. As a minimum first step all of them will recommend putting your .mdf and .ldf files on seperate drives and using Raid 10 for the .mdf file.

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise. Is it recommended. What are the pros and cons

Hi hazelannc,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How to solve bad performance in vi server

I'm useing vi server in a recursively programming structure in labview 7.1.
I have very bad performance result so i made a test comparing the speed of che various vi server call and the native.
my tests are:
normal calling.
vi server calling by reference node
vi server calling by invoke node
for each vi server calling type i tried:
unique reference calling
different reference calling
different reference, preloaded, calling
the only 1 case i found a loosing of performace acceptable 24% respect the normal calling: vi server calling by reference node with unique reference.
unfortunately this kind of calling is able to catch come kind of recunsion an forbidden it and this calling wait all the time the end of the execution of the vi called.
All the oter kinds of caling have very bad performance: from 90% to 99,9% LESS then the normal calling (10 to 1000 times more in execution time).
In addition there is a prblem in invoke colling: if you execute a invoke node with wait until done true, the mouse pointer fliks with the busy icone. that heppens in all the possible configuration.
I would like ti know if someuone as some solution to this performance problem and if Labview 8.0 fixs this problems.
Best regarda.
ing. Luca Benvegnù

Hi Luca,
I've made some researches for you and, what can I say is that there is a certain number of requests about "vi server performances". There are some things that are in general suggested in this situation:
1) Be "minimalist" about the use of images, graph,... And avoid Large data structures: wiring large structures into/out-of sub-VI's can take time: pass the smallest amount of data.
2) Avoid repeated calls. Calling the sub-VI's frequently, in a loop for example, create a call over-head that could be an issue. For the same reason put the "wait until" function with a specification of time in order to run loops only as often as strictly required.
However, about your question of fixing the problem with LabVIEW 8.0, I suggest you to download the Evaluation Version of LabVIEW 8.2 and try by yourself if performances are better.
I hope I've been of some help.
carlo>

Performance issue with database server

Hello,
We have installed ECC 6.0 on HP UX 11.23 OS with Oracle as database.
We have cluster environment in our production severs.
One server as DB-CI installed and other as Dialogue Instance installed.
After installation, the dialogue instance (Application server))works fine but if we login into DB server and execute any t-code It takes too much time or just stuck.
and after that if I go to application and execute that t-code it works fine and after that if I go to database and execute that t-code now even in DB it works fine.
Kindly guide me.
Thanks,
Chandresh Pranami.

Hi Chandresh,
Check below things for your Database server.
SM50 - Workprocess status busy or wait
ST04 - Data buffer hit ratio
SM37 - Any background job running there.
Normally even if you are login through a diffrent app server the database side execution will happen in db server only.Application server will do the execution but the data read and to be updated will happen in db server only.When the sql request will go to db server may select update..types of sql then it willalways will be processed by db server.
So there will be lot of load already thereIg you execute your work here it will take more time because more load for the application will be there.
Regards
Ashok

Essbase Studio - Failed to Establish Connection With SQL Database Server

Hi all,
I am new to Hyperion and am having trouble deploying what seems a simple cube in Essbase Studio.
My environment is Windows 2003, EPM 11.1.1.2, SQL Server 2000.
I have the following two issues which may be related.
1. The EPM System Diagnostic tool says that Hyperion Foundation cannot connect to the SQL database.
Error:
Failed: Connection to database
Error: java.net.UnknownHostException: <server name: <server name>
Recommended Action:
Every other EPM application is able to connect to the database. I have tried re-configuring Foundation Services and checking the config files and nothing looks wrong. I would appreciate advice on how to fix this.
2 In Essbase Studio, I was able to connect to the database where the source data is, build the minischema and create dimensions and measures. But when I run the cube deployment wizard I get the error:
Message: Failed to deploy Essbase cube
Caused By: Failed to build Essbase cube dimension: (Time)
Caused By: Cannot incremental build. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
…ODBC Layer Error: [08001] ==> [[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.]
I have checked the DSN as well as the connections set up within Studio, and they are all able to connect to the database. I am using the admin user for the Essbase server and have created a different user for the databases where the data resides and the shared services database. I tried using the same user all the way through and this didn’t help.
Can you please advise what else I can check or change to resolve this issue.
Also, can you work in EAS with cubes that are created in Studio? I tried looking at it and I got an error that the rule file couldn’t be accessed because it was created in Studio.
After the above failures, I tried creating a cube in EIS, with mixed success. I have been able to load the members and data without errors. But when I try to view the data in the cube, I am seeing field names for the measures instead of the data itself.
...Definitely more questions than answers at this stage of my learning.
Regards
Michelle

Michelle,
I don't know if you found an answer to you question after so many months but I was hoping I could be helpful.
The issue you are experience happens often when the dimension that you are getting an error on, in this case TIME, is built from a snowflake lineage and there is a bad foreign key reference. This dimension is most like high-up in your outline build process for Essbase Studio and this prevents the build from happening usually early on.
Check your logs also. They are in Hyperion > Products > logs > essbase > essbasestudio.
You can also make your logs more verbose by setting a configuration variable in the essbase studio server.properties file but that should only be used for debugging as it really saps performance.
And, yes, you can of course edit an Essbase Studio deployed cube in EAS. However, any changes you make to the cube in EAS are subject to being wiped-out upon the next Essbase Studio deployment of that Applicaion/Database combo.
If you want to provide more detail, screenshots, etc. I would be glad to help where I can.
Cheers,
Christian
http://www.artofbi.com

Bad performance, nvidia 6800GT, v.180.22

Hi,
The following text was written for some minutes ago.. Turns out, I got some new (strange) information. Please read the update below.
Just though I'd help out people who might have been in the same situation as I was; after upgrading to kernel 2.6.28 and nvidia 180.22 driver I got terrible performance when viewing videos. Even Firefox lagged when I scrolled my Twitter page. So, as I was starting to check how to downgrade, I also read nvidia wiki here on Arch linux. It turns out that my xorg config was missing one simple line which made my life better:
Option "TripleBuffer" "True"
I haven't done a thing with my xorg conf since the upgrade, so I dunno why it worked better without these three words with my old driver (v.177.82)
Anyways, hope this helps someone else out too
UPDATE:
Okai, so I restarted my computer and it turned out to be just as bad as before ..What I did when it got better was to edit the xorg cong and restart x with ctrl+alt+backspace.. So, after the restart and when I found out that the video once again was lagging i just restarted x with ctrl+alt+backspace and suddenly I could play videos without lag. wtf? So, if anyone could try to explain this to me, I'd be once again happy. Thank you! :-)
UPDATE 2:
It seems that a cause of the problem can be found in post 12 in this thread.
Last edited by siaco (2009-01-23 16:47:25)

toketin wrote:siaco and johnny can you paste your xorg.0.log in /var/log when you turn on your pc and so you have the slow session and when you restart X please? My curiosity have you only a videocard or an integrated one too?
Right after restart of computer:
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux hitman 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 18 20:17:17 UTC 2009 i686
Build Date: 17 December 2008 08:20:05PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 23 07:17:51 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d5fe0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@1:0:0) nVidia Corporation NV40 [GeForce 6800 GT] rev 161, Mem @ 0xf8000000/0, 0xe0000000/0, 0xf9000000/0, BIOS @ 0x????????/131072
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 180.22 Tue Jan 6 09:58:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.22 Tue Jan 6 09:35:46 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TripleBuffer" "true"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 6800 GT (NV40) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.40.02.15.01
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6800 GT at PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (DFP-0)
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 155.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(II) config/hal: Adding input device Logitech USB Gaming Mouse
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.1
(**) Logitech USB Gaming Mouse: always reports core events
(**) Logitech USB Gaming Mouse: Device: "/dev/input/event4"
(II) Logitech USB Gaming Mouse: Found 16 mouse buttons
(II) Logitech USB Gaming Mouse: Found x and y relative axes
(II) Logitech USB Gaming Mouse: Configuring as mouse
(**) Logitech USB Gaming Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB Gaming Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Gaming Mouse" (type: MOUSE)
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) AT Translated Set 2 keyboard: xkb_model: "evdev"
(**) Option "xkb_layout" "no"
(**) AT Translated Set 2 keyboard: xkb_layout: "no"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6344 )
AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6345 )
AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6346 )
After restarting of X
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux hitman 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 18 20:17:17 UTC 2009 i686
Build Date: 17 December 2008 08:20:05PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 23 07:20:02 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d5fe0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@1:0:0) nVidia Corporation NV40 [GeForce 6800 GT] rev 161, Mem @ 0xf8000000/0, 0xe0000000/0, 0xf9000000/0, BIOS @ 0x????????/131072
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 180.22 Tue Jan 6 09:58:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.22 Tue Jan 6 09:35:46 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TripleBuffer" "true"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 6800 GT (NV40) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.40.02.15.01
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6800 GT at PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (DFP-0)
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 155.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (90, 88); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(II) config/hal: Adding input device Logitech USB Gaming Mouse
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.1
(**) Logitech USB Gaming Mouse: always reports core events
(**) Logitech USB Gaming Mouse: Device: "/dev/input/event4"
(II) Logitech USB Gaming Mouse: Found 16 mouse buttons
(II) Logitech USB Gaming Mouse: Found x and y relative axes
(II) Logitech USB Gaming Mouse: Configuring as mouse
(**) Logitech USB Gaming Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB Gaming Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Gaming Mouse" (type: MOUSE)
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) AT Translated Set 2 keyboard: xkb_model: "evdev"
(**) Option "xkb_layout" "no"
(**) AT Translated Set 2 keyboard: xkb_layout: "no"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6636 )
AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6637 )
AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6638 )
Diff:
diff Xorg.bad.log Xorg.good.log
14c14
< (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 23 07:17:51 2009
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 23 07:20:02 2009
263a264
> (II) NVIDIA(0): Detected AGP rate: 8X
343c344
< (II) NVIDIA(0): Initialized GPU GART.
> (II) NVIDIA(0): Initialized AGP GART.
415,417c416,418
< AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6344 )
< AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6345 )
< AUDIT: Fri Jan 23 07:18:24 2009: 6324 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6346 )
> AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6636 )
> AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6637 )
> AUDIT: Fri Jan 23 07:20:10 2009: 6620 Xorg: client 4 rejected from local host ( uid=1000 gid=100 pid=6638 )
So it turns out, (II) NVIDIA(0): Detected AGP rate: 8X is only found in the "good"-log This corresponds well with what danielomen suggested too; when I checked nvidia-settings it said PCI on bus type and after restarting X it said AGP 8X.

Increase Performance and ROI for SQL Server Environments

May 2015
Explore
The Buzz from Microsoft Ignite 2015
NetApp was in full force at the recent Microsoft Ignite show in Chicago, talking about solutions for hybrid cloud, and our proven solutions for Microsoft SQL Server and other Microsoft applications.
Hot topics at the NetApp booth included:
OnCommand® Shift. A revolutionary technology that lets you move virtual machines back and forth between VMware and Hyper-V environments in minutes.
Azure Site Recovery to NetApp Private Storage. Replicate on-premises SAN-based applications to NPS for disaster recovery in the Azure cloud.
These tools give you greater flexibility for managing and protecting important business applications.
Chris Lemmons
Director, EIS Technical Marketing, NetApp
If your organization runs databases such as Microsoft SQL Server and Oracle DB, you probably know that these vendors primarily license their products on a "per-core" basis. Microsoft recently switched to "per-core" rather than "per-socket" licensing for SQL Server 2012 and 2014. This change can have a big impact on the total cost of operating a database, especially as core counts on new servers continue to climb. It turns out that the right storage infrastructure can drive down database costs, increase productivity, and put your infrastructure back in balance.
In many customer environments, NetApp has noticed that server CPU utilization is low—often on the order of just 20%. This is usually the result of I/O bottlenecks. Server cores have to sit and wait for I/O from hard disk drives (HDDs). We've been closely studying the impact of all-flash storage on SQL Server environments that use HDD-based storage systems. NetApp® All Flash FAS platform delivers world-class performance for SQL Server plus the storage efficiency, application integration, nondisruptive operations, and data protection of clustered Data ONTAP®, making it ideal for SQL Server environments.
Tests show that All Flash FAS can drive up IOPS and database server CPU utilization by as much as 4x. And with a 95% reduction in latency, you can achieve this level of performance with half as many servers. This reduces the number of servers you need and the number of cores you have to license, driving down costs by 50% or more and paying back your investment in flash in as little as six months.
Figure 1) NetApp All Flash FAS increases CPU utilization on your SQL Server database servers, lowering costs.
Source: NetApp, 2015
Whether you're running one of the newer versions of SQL Server or facing an upgrade of an earlier version, you can't afford not to take a second look at your storage environment.
End of Support for Microsoft SQL Server 2005 is Rapidly Approaching
Microsoft has set the end of extended support for SQL Server 2005 for April 2016—less than a year away. With support for Microsoft Windows 2003 ending in July 2015, time may already be running short.
If you're running Windows Server 2003, new server hardware is almost certainly needed when you upgrade SQL Server. Evaluate your server and storage options now to get costs under control.
Test Methodology
To test the impact of flash on SQL Server performance, we replaced a legacy HDD-based storage system with an All Flash FAS AFF8080 EX. The legacy system was configured with almost 150 HDDs, a typical configuration for HDD storage supporting SQL Server. The AFF8080 EX used just 48 SSDs.
Table 1) Components used in testing.
Test Configuration Components
Details
SQL Server 2014 servers
Fujitsu RX300
Server operating system
Microsoft Windows 2012 R2 Standard Edition
SQL Server database version
Microsoft SQL Server 2014 Enterprise Edition
Processors per server
2 6-core Xeon E5-2630 at 2.30 GHz
Fibre channel network
8Gb FC with multipathing
Storage controller
AFF8080 EX
Data ONTAP version
Clustered Data ONTAP® 8.3.1
Drive number and type
48 SSD
Source: NetApp, 2015
The test configuration consisted of 10 database servers connected through fibre channel to both the legacy storage system and the AFF8080 EX. Each of the 10 servers ran SQL Server 2014 Enterprise Edition.
The publicly available HammerDB workload generator was used to drive an OLTP-like workload simultaneously from each of the 10 database servers to storage. We first directed the workload to the legacy storage array to establish a baseline, increasing the load to the point where read latency consistently exceeded 20ms.
That workload was then directed at the AFF8080 EX. The change in storage resulted in an overall 20x reduction in read latency, a greater than 4x improvement in IOPS, and a greater than 4x improvement in database server CPU utilization.
Figure 2) NetApp All Flash FAS increases IOPS and server CPU utilization and lowers latency.
Source: NetApp, 2015
In other words, the database servers are able to process four times as many IOPS with dramatically lower latency. CPU utilization goes up accordingly because the servers are processing 4x the work per unit time.
The All Flash FAS system still had additional headroom under this load.
Calculating the Savings
Let's look at what this performance improvement means for the total cost of running SQL Server 2014 over a 3-year period. To do the analysis we used NetApp Realize, a storage modeling and financial analysis tool designed to help quantify the value of NetApp solutions and products. NetApp sales teams and partners use this tool to assist with return on investment (ROI) calculations.
The calculation includes the cost of the AFF8080 EX, eliminates the costs associated with the existing storage system, and cuts the total number of database servers from 10 to five. This reduces SQL Server licensing costs by 50%. The same workload was run with five servers and achieved the same results. ROI analysis is summarized in Table 2.
Table 2) ROI from replacing an HDD-based storage system with All Flash FAS, thereby cutting server and licensing costs in half.
Value
Analysis Results
ROI
65%
Net present value (NPV)
$950,000
Payback period
six months
Total cost reduction
More than $1 million saved over a 3-year analysis period compared to the legacy storage system
Savings on power, space, and administration
$40,000
Additional savings due to nondisruptive operations benefits (not included in ROI)
$90,000
Source: NetApp, 2015
The takeaway here is that you can replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs, with the majority of the savings derived from the reduction in SQL Server licensing costs.
Replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs.
Maximum SQL Server 2014 Performance
In addition to the ROI analysis, we also measured the maximum performance of the AFF8080 EX with SQL Server 2014. A load-generation tool was used to simulate an industry-standard TPC-E OLTP workload against an SQL Server 2014 test configuration.
A two-node AFF8080 EX achieved a maximum throughput of 322K IOPS at just over 1ms latency. For all points other than the maximum load point, latency was consistently under 1ms and remained under 0.8ms up to 180K IOPS.
Data Reduction and Storage Efficiency
In addition to performance testing, we looked at the overall storage efficiency savings of our SQL Server database implementation. The degree of compression that can be achieved is dependent on the actual data that is written and stored in the database. For this environment, inline compression was effective. Deduplication, as is often the case in database environments, provided little additional storage savings and was not enabled.
For the test data used in the maximum performance test, we measured a compression ratio of 1.5:1. We also tested inline compression on a production SQL Server 2014 data set to further validate these results and saw a 1.8:1 compression ratio.
Space-efficient NetApp Snapshot® copies provide additional storage efficiency benefits for database environments. Unlike snapshot methods that use copy-on-write, there is no performance penalty; unlike full mirror copies, NetApp Snapshot copies use storage space sparingly. Snapshot copies only consume a small amount of storage space for metadata and additional incremental space is consumed as block-level changes occur. In a typical real-world SQL Server deployment on NetApp storage, database volume Snapshot copies are made every two hours.
First introduced more than 10 years ago, NetApp FlexClone® technology also plays an important role in SQL Server environments. Clones are fully writable, and, similar to Snapshot copies, only consume incremental storage capacity. With FlexClone, you can create as many copies of production data as you need for development and test, reporting, and so on. Cloning is a great way to support the development and test work needed when upgrading from an earlier version of SQL Server. You'll sometimes see these types of capabilities referred to as "copy data management."
A Better Way to Run Enterprise Applications
The performance benefits that all-flash storage can deliver for database environments are significant: more IOPS, lower latency, and an end to near-constant performance tuning.
If you think the performance acceleration that comes with all-flash storage is cost prohibitive, think again. All Flash FAS doesn't just deliver a performance boost, it changes the economics of your operations, paying for itself with thousands in savings on licensing and server costs. In terms of dollars per IOPS, All Flash FAS is extremely economical relative to HDD.
And, because All Flash FAS runs NetApp clustered Data ONTAP, it delivers the most complete environment to support SQL Server and all your enterprise applications with capabilities that include comprehensive storage efficiency, integrated data protection, and deep integration for your applications.
For complete details on this testing look for NetApp TR-4303, which will be available in a few weeks. Stay tuned to Tech OnTap for more information as NetApp continues to run benchmarks with important server workloads including Oracle DB and server virtualization.
Learn more about NetApp solutions for SQL Server and NetApp All-flash solutions.
Quick Links
Tech OnTap Community
Archive
PDF

May 2015
Explore
The Buzz from Microsoft Ignite 2015
NetApp was in full force at the recent Microsoft Ignite show in Chicago, talking about solutions for hybrid cloud, and our proven solutions for Microsoft SQL Server and other Microsoft applications.
Hot topics at the NetApp booth included:
OnCommand® Shift. A revolutionary technology that lets you move virtual machines back and forth between VMware and Hyper-V environments in minutes.
Azure Site Recovery to NetApp Private Storage. Replicate on-premises SAN-based applications to NPS for disaster recovery in the Azure cloud.
These tools give you greater flexibility for managing and protecting important business applications.
Chris Lemmons
Director, EIS Technical Marketing, NetApp
If your organization runs databases such as Microsoft SQL Server and Oracle DB, you probably know that these vendors primarily license their products on a "per-core" basis. Microsoft recently switched to "per-core" rather than "per-socket" licensing for SQL Server 2012 and 2014. This change can have a big impact on the total cost of operating a database, especially as core counts on new servers continue to climb. It turns out that the right storage infrastructure can drive down database costs, increase productivity, and put your infrastructure back in balance.
In many customer environments, NetApp has noticed that server CPU utilization is low—often on the order of just 20%. This is usually the result of I/O bottlenecks. Server cores have to sit and wait for I/O from hard disk drives (HDDs). We've been closely studying the impact of all-flash storage on SQL Server environments that use HDD-based storage systems. NetApp® All Flash FAS platform delivers world-class performance for SQL Server plus the storage efficiency, application integration, nondisruptive operations, and data protection of clustered Data ONTAP®, making it ideal for SQL Server environments.
Tests show that All Flash FAS can drive up IOPS and database server CPU utilization by as much as 4x. And with a 95% reduction in latency, you can achieve this level of performance with half as many servers. This reduces the number of servers you need and the number of cores you have to license, driving down costs by 50% or more and paying back your investment in flash in as little as six months.
Figure 1) NetApp All Flash FAS increases CPU utilization on your SQL Server database servers, lowering costs.
Source: NetApp, 2015
Whether you're running one of the newer versions of SQL Server or facing an upgrade of an earlier version, you can't afford not to take a second look at your storage environment.
End of Support for Microsoft SQL Server 2005 is Rapidly Approaching
Microsoft has set the end of extended support for SQL Server 2005 for April 2016—less than a year away. With support for Microsoft Windows 2003 ending in July 2015, time may already be running short.
If you're running Windows Server 2003, new server hardware is almost certainly needed when you upgrade SQL Server. Evaluate your server and storage options now to get costs under control.
Test Methodology
To test the impact of flash on SQL Server performance, we replaced a legacy HDD-based storage system with an All Flash FAS AFF8080 EX. The legacy system was configured with almost 150 HDDs, a typical configuration for HDD storage supporting SQL Server. The AFF8080 EX used just 48 SSDs.
Table 1) Components used in testing.
Test Configuration Components
Details
SQL Server 2014 servers
Fujitsu RX300
Server operating system
Microsoft Windows 2012 R2 Standard Edition
SQL Server database version
Microsoft SQL Server 2014 Enterprise Edition
Processors per server
2 6-core Xeon E5-2630 at 2.30 GHz
Fibre channel network
8Gb FC with multipathing
Storage controller
AFF8080 EX
Data ONTAP version
Clustered Data ONTAP® 8.3.1
Drive number and type
48 SSD
Source: NetApp, 2015
The test configuration consisted of 10 database servers connected through fibre channel to both the legacy storage system and the AFF8080 EX. Each of the 10 servers ran SQL Server 2014 Enterprise Edition.
The publicly available HammerDB workload generator was used to drive an OLTP-like workload simultaneously from each of the 10 database servers to storage. We first directed the workload to the legacy storage array to establish a baseline, increasing the load to the point where read latency consistently exceeded 20ms.
That workload was then directed at the AFF8080 EX. The change in storage resulted in an overall 20x reduction in read latency, a greater than 4x improvement in IOPS, and a greater than 4x improvement in database server CPU utilization.
Figure 2) NetApp All Flash FAS increases IOPS and server CPU utilization and lowers latency.
Source: NetApp, 2015
In other words, the database servers are able to process four times as many IOPS with dramatically lower latency. CPU utilization goes up accordingly because the servers are processing 4x the work per unit time.
The All Flash FAS system still had additional headroom under this load.
Calculating the Savings
Let's look at what this performance improvement means for the total cost of running SQL Server 2014 over a 3-year period. To do the analysis we used NetApp Realize, a storage modeling and financial analysis tool designed to help quantify the value of NetApp solutions and products. NetApp sales teams and partners use this tool to assist with return on investment (ROI) calculations.
The calculation includes the cost of the AFF8080 EX, eliminates the costs associated with the existing storage system, and cuts the total number of database servers from 10 to five. This reduces SQL Server licensing costs by 50%. The same workload was run with five servers and achieved the same results. ROI analysis is summarized in Table 2.
Table 2) ROI from replacing an HDD-based storage system with All Flash FAS, thereby cutting server and licensing costs in half.
Value
Analysis Results
ROI
65%
Net present value (NPV)
$950,000
Payback period
six months
Total cost reduction
More than $1 million saved over a 3-year analysis period compared to the legacy storage system
Savings on power, space, and administration
$40,000
Additional savings due to nondisruptive operations benefits (not included in ROI)
$90,000
Source: NetApp, 2015
The takeaway here is that you can replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs, with the majority of the savings derived from the reduction in SQL Server licensing costs.
Replace your existing storage with All Flash FAS and get a big performance bump while substantially reducing your costs.
Maximum SQL Server 2014 Performance
In addition to the ROI analysis, we also measured the maximum performance of the AFF8080 EX with SQL Server 2014. A load-generation tool was used to simulate an industry-standard TPC-E OLTP workload against an SQL Server 2014 test configuration.
A two-node AFF8080 EX achieved a maximum throughput of 322K IOPS at just over 1ms latency. For all points other than the maximum load point, latency was consistently under 1ms and remained under 0.8ms up to 180K IOPS.
Data Reduction and Storage Efficiency
In addition to performance testing, we looked at the overall storage efficiency savings of our SQL Server database implementation. The degree of compression that can be achieved is dependent on the actual data that is written and stored in the database. For this environment, inline compression was effective. Deduplication, as is often the case in database environments, provided little additional storage savings and was not enabled.
For the test data used in the maximum performance test, we measured a compression ratio of 1.5:1. We also tested inline compression on a production SQL Server 2014 data set to further validate these results and saw a 1.8:1 compression ratio.
Space-efficient NetApp Snapshot® copies provide additional storage efficiency benefits for database environments. Unlike snapshot methods that use copy-on-write, there is no performance penalty; unlike full mirror copies, NetApp Snapshot copies use storage space sparingly. Snapshot copies only consume a small amount of storage space for metadata and additional incremental space is consumed as block-level changes occur. In a typical real-world SQL Server deployment on NetApp storage, database volume Snapshot copies are made every two hours.
First introduced more than 10 years ago, NetApp FlexClone® technology also plays an important role in SQL Server environments. Clones are fully writable, and, similar to Snapshot copies, only consume incremental storage capacity. With FlexClone, you can create as many copies of production data as you need for development and test, reporting, and so on. Cloning is a great way to support the development and test work needed when upgrading from an earlier version of SQL Server. You'll sometimes see these types of capabilities referred to as "copy data management."
A Better Way to Run Enterprise Applications
The performance benefits that all-flash storage can deliver for database environments are significant: more IOPS, lower latency, and an end to near-constant performance tuning.
If you think the performance acceleration that comes with all-flash storage is cost prohibitive, think again. All Flash FAS doesn't just deliver a performance boost, it changes the economics of your operations, paying for itself with thousands in savings on licensing and server costs. In terms of dollars per IOPS, All Flash FAS is extremely economical relative to HDD.
And, because All Flash FAS runs NetApp clustered Data ONTAP, it delivers the most complete environment to support SQL Server and all your enterprise applications with capabilities that include comprehensive storage efficiency, integrated data protection, and deep integration for your applications.
For complete details on this testing look for NetApp TR-4303, which will be available in a few weeks. Stay tuned to Tech OnTap for more information as NetApp continues to run benchmarks with important server workloads including Oracle DB and server virtualization.
Learn more about NetApp solutions for SQL Server and NetApp All-flash solutions.
Quick Links
Tech OnTap Community
Archive
PDF

Bad performance: Xpath View causes database server almost 100% cpu

Similar Messages

Maybe you are looking for