JanusGraph HBase table with too much column families

[RaulGuo]

It is advised in hbase that there should be less than three column families in a HBase table, if we create a table with more than that, it will have bad effect for the hbase performance because many extra IO of small files. But as far as I know, JanusGraph with hbase as storage backend will create table with nine column families, does that have bad influence for HBase performance? If so, is there any way to avoid it or improve the situation?