[SOLVED] Re: kworker eats 45% from first cpu

2017-01-09 Thread deloptes
deloptes wrote: > deloptes wrote: > >> Hi community, >> I moved my system to an SSD two days ago. I applied recommendation to >> use "discard" when I noticed that one kworker is using exactly 45% of the >> first cpu. > > > perf says > > > 55.13% [kernel] [k] acpi_

Re: kworker eats 45% from first cpu

2017-01-09 Thread deloptes
deloptes wrote: > Hi community, > I moved my system to an SSD two days ago. I applied recommendation to > use "discard" when I noticed that one kworker is using exactly 45% of the > first cpu. perf says 55.13% [kernel] [k] acpi_os_read_port 26.65% [kernel]

Re: kworker eats 45% from first cpu

2017-01-08 Thread deloptes
Jochen Spieker wrote: > Jochen Spieker: >> deloptes: >>> >>> I moved my system to an SSD two days ago. I applied recommendation to >>> use "discard" >> >> What do you mean by that? If you are talking about the mount >> option, discard it. (Sorry for the pun.) Use a weekly cron job with >> 'fstri

Re: kworker eats 45% from first cpu

2017-01-08 Thread Jochen Spieker
Jochen Spieker: > deloptes: >> >> I moved my system to an SSD two days ago. I applied recommendation to >> use "discard" > > What do you mean by that? If you are talking about the mount > option, discard it. (Sorry for the pun.) Use a weekly cron job with > 'fstrim -a' instead. If you are using L

Re: kworker eats 45% from first cpu

2017-01-08 Thread Jochen Spieker
deloptes: > > I moved my system to an SSD two days ago. I applied recommendation to > use "discard" What do you mean by that? If you are talking about the mount option, discard it. (Sorry for the pun.) Use a weekly cron job with 'fstrim -a' instead. If you are using LVM, set issue_discards=1 in /e