Database performance for one alert with multiple triggers?

Most of our sites that have Solarwinds Alerts set up only need: High response time, restarted node, down node, packet loss alerts and high interface usage.  

Is it more taxing on the Database to have one alert that checks for restarts, down node, loss packets, and response time or should I break that up into 4 different Alerts?  

I would like to cut back on multiple alerts (a down node will also trigger a packet loss alert for example) and at the same time, minimize the effort to create new site alerts.

I have about 10 different alerting groups I'm managing (2 alerts per site) and would really like to have 15 Alerts total verses 50 but also don't want to cause slowness in our system.