Re: Rationale for multiple activity tables?
Is there already logic in the code that would allow me to configure that users 1-1000 have activity on server1 (associated with specific DSN params), users 1001-2000 have activity logs on server2 (separate DSN) etc.? I’m not seeing it in the code, but I might be overlooking something.
I’d think using an innodb table type and allowing the db to handle table partitioning/sharding at the db level would make more sense for people concerned about running across multiple servers. Have there been experiences with large BP installations that would run counter to that way of thinking?