1 big merge publication or N small ones?
I've been looking for an answer to no avail.

However, I've found a place where some advantages are mentioned:


Easier to maintain.
Multiple data streams going to the subscription database at once (hopefully).
If the merge fails for a publication, only this publication has to be fixed and reinitialized.


So I think there would be no performance improvement having just 1 big one publication. On the contrary, if the data streams are parallel, we can even get a better performance when splitting the merge in N small publications.