all groups > sql server full text search > january 2007 >
You're in the

sql server full text search

group:

page faults


page faults CR
1/18/2007 7:05:41 AM
sql server full text search:
Our performance is currently fine, but we are planning on adding more full
text indexes, so I have question.
Our database server is experiencing between 2,000 and 10,000 page faults
per second on msftesql.exe, as shown in task manager on the processes tab,
is this normal for a relatively busy website (50
million hits daily) with full text?


Re: page faults CR
1/18/2007 8:17:31 AM
Ok, that brings up another question, our server is set to boost SQL Server
priority, would this slow down msftesql? We are running 4 3.2 Xeon's with 8
GB RAM (Maxmem is set to 7168 MB). We have 14 fulltext indexes with
approximately a million rows each, but within the next month we will be
adding 12 more fulltext indexes which, I believe, will be slightly larger,
and doubling our db size (currently we have 63 tables, the largest being 10
million rows, and total used mdf size is 17 GB). Do you think the boost SQL
Server setting will be slowing fulltext indexing? Or does this setting also
boost the priority of msftesql? Do you think the max memory setting above is
giving msftesql the room it needs?
Thanks.
CR

[quoted text, click to view]

Re: page faults Hilary Cotter
1/18/2007 8:41:48 AM
This is normal, you might want to limit max memory size to something smaller
to give room for MSFTESQL.

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

Re: page faults Simon Sabin
1/18/2007 8:32:45 PM
Hello cr,

I would say that memory setting doesn't allow for much room for the OS, FT
and anything else on the box.

I assume this is a 64 bit server running sql 2005.

I would strongly advise more memory. You will currently be running mostly
out of memory, doubling the size of your DB will not enable you to do that,
which may have serious consequences depending on how your data is used.


Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons


[quoted text, click to view]

Re: page faults Hilary Cotter
1/22/2007 7:58:01 AM
While I can't speak for Simon's experience, we are running with 16 Gigs on a
x64 bit machine (DL 585) and its running fine. We have set our max memory to
give 1 Gig to the OS (and SQL FTS).

Your results may vary - you have to study whether memory is a bottle neck
for you - it isn't for us.

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

AddThis Social Bookmark Button