The amount of data depends on what each IP address is doing, that is why by default it is aggregated.
By turning off the aggregation you are taking that /24 aggregation, 10.100.1.0-10.100.1.255, and saying 'actually show me what type of traffic volume for EACH port that is going over EACH IP address in that range'.
As you disable aggregation, you may also open yourself up to maxing out your cache limits. This can be easily checked and adjusted, but the values there were also set to prevent the DB explosion Adam described.
So the answer isn't a clear cut one because it'll vary based on the amount of different /24's it is aggregating and the different types of traffic within those ranges.
Another way forward would be to do a traffic capture on that range for a few minutes, identify the IP/Port combo that is really important to you and make it a software service and application. This way you are not going to drown yourself in data you don't care about but can solely focus on that needle in this haystack so to speak.