You wouldn't normally use CQRS for CRUD scenarios. There are way simpler tools and patterns to create CRUDy applications.
CQRS brings many advantages to behavior-rich scenarios, where the verbs are not Create, Read, Update, Delete, but rather resemble real behavior. Like PromoteEmployee or BlacklistVendor.
Once you start modelling a behavior-rich domain, there might still be many corelating commands/events - which isn't a bad thing -, but you will also find that commands and the resulting events can be very different both in size (data contained) and in numbers.