What does DIRECT do in Eon?

It does nothing. Always goes to ROS and we say data is committed after we have the data on S3.

Interesting. So if we were comparing load times between Enterprise and Eon (same number of nodes and shards=nodes). Eon would always come out slower because it needs to sync the data into S3 and is limited by S3 speeds. Am I right in saying that?

Not entirely, on Enterprise we need to ship the ROS containers to the buddy nodes, on Eon we need to ship the containers to S3. Loading direct should be very similar on Eon and Enterprise.

Got it!

Any way today for Vertica to load data ONLY to the depot? (And maybe background the sync to S3). And the reverse -> any way to load data directly to S3 and skip depot?

I see options DisableDirectToCommunalStorageWrites and UseDepotForWrites. Though both seem to be similar in function. Any experience in using these?

https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/ConfiguringTheDB/EonModeParameters.htm

Thanks Carlos!

Not committing the data to S3 means that if that node goes down you loose data. Not sure if it's something we want to do. Regarding the settings I'm not familiar with them, I think we need to have better descriptions to clarify what they do.