Comment 17 for bug 458453

I think I may be seeing the same problem, only it's not ubuntu one related. I'm using Ubuntu 10.04 but I don't use ubuntu one (I don't even have an account). Periodically beam.smp CPU usage spikes for several minutes, then goes back to normal. I've looked at $HOME/.cache/desktop-couch/desktop-couchdb.log.1 and there's lot of messages like these:

[Sat, 31 Jul 2010 08:42:01 GMT] [info] [<0.8130.3>] 127.0.0.1 - - 'HEAD' /gwibber_accounts 401^M
^M
[Sat, 31 Jul 2010 08:42:01 GMT] [info] [<0.8130.3>] 127.0.0.1 - - 'HEAD' /gwibber_accounts 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8130.3>] 127.0.0.1 - - 'HEAD' /gwibber_accounts 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8130.3>] 127.0.0.1 - - 'GET' /gwibber_accounts 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8134.3>] 127.0.0.1 - - 'HEAD' /gwibber_messages 401^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8134.3>] 127.0.0.1 - - 'HEAD' /gwibber_messages 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8134.3>] 127.0.0.1 - - 'HEAD' /gwibber_messages 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8134.3>] 127.0.0.1 - - 'GET' /gwibber_messages 200^M
^M
[Sat, 31 Jul 2010 08:42:02 GMT] [info] [<0.8130.3>] 127.0.0.1 - - 'GET' /gwibber_accounts/twitter-amatriain 200^M

It seems to me this is Gwibber related, specifically the way gwibber handles twitter. I do use gwibber for my twitter and facebook accounts.