Jump to content

Custom Domain size: how big is too big?

Go to solution Solved by hozawa,

Recommended Posts

What restrictions or best-practices should be adhered to when constructing a custom Domain?  In other words: "How big is too big"?  As long as it is manageable by a human, how much can the system handle? 

Questions I've considered:

  • Number of joins?
  • Number of Tables or Derived Tables?
  • Number of Sets and Displayed Fields?
  • Datasource type / technology limitations?
  • Computer specification or powere needed?  (client- or server-side)
  • When will Views and Reports become unusable or unstable?
Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

  • Solution

I think it mostly depends on response time when using the domain. This depends on the server performance, network performance, and datasource performance. I personally don't recommend using domain because of memory usage and performance. I just create a new table using Jaspersoft ETL (Talend ETL) and use that because disk space is very cheap nowadays.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...