Re: 7-Current: turn off debugging (kqread?)

2007-07-30 Thread Kevin Kramer
yes. i got an answer on current. even though my host was not setup as a 
NIS client, it was trying to resolve UID/GID information. the only line 
in my rc.conf was NISDOMAIN=


--

Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com



Kris Kennaway wrote the following on 07/27/07 15:12:

On Tue, Jul 03, 2007 at 11:12:36AM -0500, Kevin Kramer wrote:
  
thanks. I rebuild this morning with this and still no change. I can't 
even find any info on these flags...



Dunno if anyone ever gave you the real answer to your question, but if
not then here it is: your DNS is broken and taking ages to respond to
lookups (or more likely, not responding at all).  kqread means the
application is waiting to read more data from an I/O request.  It's
not a 7.0 optimization issue.

Kris
  

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 7-Current: turn off debugging (kqread?)

2007-07-27 Thread Kris Kennaway
On Tue, Jul 03, 2007 at 11:12:36AM -0500, Kevin Kramer wrote:
> thanks. I rebuild this morning with this and still no change. I can't 
> even find any info on these flags...

Dunno if anyone ever gave you the real answer to your question, but if
not then here it is: your DNS is broken and taking ages to respond to
lookups (or more likely, not responding at all).  kqread means the
application is waiting to read more data from an I/O request.  It's
not a 7.0 optimization issue.

Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 7-Current: turn off debugging (kqread?)

2007-07-03 Thread Kevin Kramer
thanks. I rebuild this morning with this and still no change. I can't 
even find any info on these flags...


Pieter de Goeje wrote:

On Friday 29 June 2007, Kevin Kramer wrote:
  

yes. that is where I have started, but I cannot get buildkernel to build
with those commented out. the UPDATING file also lists heavy debugging
turned on in userland, which I can't track down to any config files.

Add CFLAGS+= -DMALLOC_PRODUCTION to make.conf and rebuild world (or just 
libc). It boosted performance for my app (with a lot of embedded lua) by 20%.


HTH,
Pieter de Goeje
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
  

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 7-Current: turn off debugging (kqread?)

2007-07-02 Thread Pieter de Goeje
On Friday 29 June 2007, Kevin Kramer wrote:
> yes. that is where I have started, but I cannot get buildkernel to build
> with those commented out. the UPDATING file also lists heavy debugging
> turned on in userland, which I can't track down to any config files.
Add CFLAGS+= -DMALLOC_PRODUCTION to make.conf and rebuild world (or just 
libc). It boosted performance for my app (with a lot of embedded lua) by 20%.

HTH,
Pieter de Goeje
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 7-Current: turn off debugging (kqread?)

2007-06-29 Thread Kevin Kramer
yes. that is where I have started, but I cannot get buildkernel to build 
with those commented out. the UPDATING file also lists heavy debugging 
turned on in userland, which I can't track down to any config files.


I've cvsup'ng now to see if I can build today.

Tom Evans wrote the following on 06/29/07 11:13:

On Fri, 2007-06-29 at 09:34 -0500, Kevin Kramer wrote:
  
I know that debugging is turned on everywhere on 7-Current and I've read 
UPDATING. But what I can't find is how to turn off debugging. I've tried 
removing all debugging from the kernel, but it won't build. I can't find 
any userland debugging notes to turn it off.


It is taking literally 5 minutes to login to my host and the same amount 
of time to run top. Processes get stuck in kqread. Maybe this is not a 
7-Current debugging problem, but I need some guidance on where to go or 
what to look for.


Any help appreciated.



In your kernel config, remove these lines if they exist:

options INVARIANTS  # Enable calls of extra sanity
checking
options INVARIANT_SUPPORT   # Extra sanity checks of
internal structures, required by INVARIANTS
options WITNESS # Enable checks to detect
deadlocks and cycles
options WITNESS_SKIPSPIN# Don't run witness on spinlocks
for speed

You can leave the "options {K,D,G}DB" lines, they incur virtually now
performance costs.

You would get more help (possibly) if you tried posting on current@

  

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 7-Current: turn off debugging (kqread?)

2007-06-29 Thread Tom Evans
On Fri, 2007-06-29 at 09:34 -0500, Kevin Kramer wrote:
> I know that debugging is turned on everywhere on 7-Current and I've read 
> UPDATING. But what I can't find is how to turn off debugging. I've tried 
> removing all debugging from the kernel, but it won't build. I can't find 
> any userland debugging notes to turn it off.
> 
> It is taking literally 5 minutes to login to my host and the same amount 
> of time to run top. Processes get stuck in kqread. Maybe this is not a 
> 7-Current debugging problem, but I need some guidance on where to go or 
> what to look for.
> 
> Any help appreciated.

In your kernel config, remove these lines if they exist:

options INVARIANTS  # Enable calls of extra sanity
checking
options INVARIANT_SUPPORT   # Extra sanity checks of
internal structures, required by INVARIANTS
options WITNESS # Enable checks to detect
deadlocks and cycles
options WITNESS_SKIPSPIN# Don't run witness on spinlocks
for speed

You can leave the "options {K,D,G}DB" lines, they incur virtually now
performance costs.

You would get more help (possibly) if you tried posting on current@



signature.asc
Description: This is a digitally signed message part