We're using and learning Domo, and I'm checking out some alternatives as they come up. The Magic ETL DataFlow editor is slick. I'm not normall one for visual programming tools but, dang, that window is impressive.
Here's my test setup. I've got a DataSet with about 220K rows. It lumps together data from a variety of facilities into the one DataSource. This is very convenient for the import and seems fine. Once inside Domo most, if not all, cards and pages will only pull data from one facility out of the full DataSet. So, imagine out of the 220K rows that any one card/page only needs 5-10K of the records, max.
I just tried out a simple DataFlow that produces a new DataSet for one facility by using a simple filter rule. Here's the question, is there any point? I don't know enough (anything) about Domo's internals. Will I see any speed advantage to having pre-created a smaller DataSet for individual facilities? For all I know, the DataFlow is functionally a mask and I'll see no benefit. Or, it could be making a duplicate set with its own indexes and I will. And, for all I know, page filters may already do that sort of work behind the scenes automatically.
I know that my example row counts are small - but they'll grow. I figured I'd ask about alternatives now before we've sunk a lot of time into any particular approach.
Thanks very much! I've been getting great answers here, much appreciated.