How much dependency properties is too much?

I have a WPF MVVM program. One of my View/ ViewModel pairs is for program settings. When I started to develop 2 years ago there were about 15 settings, and all was good.

Today , in the Nth version, there are about 80 settings. Visually (UI) they are divided into tabs. Logically there still is one View and one ViewModel with 80 dependency properties.

It all works, but somehow doesn't feel good or correct to have a class with 80 dependency properties.

What do you think?