Re: [Gtkwave-users] vcd2lxt2 performance writing to NFS disk (fseek & zlib)
Brought to you by:
gtkwave,
joel1234567
From: <by...@nc...> - 2019-01-31 06:12:13
|
That option should be safe and it should always be faster/smaller. The intended purpose of checkpoints (and FST does this as well) is to allow block splicing tools that allow, for example, chopping the front and/or back blocks in time off a simulation, but I never wrote them for LXT2 or FST. -Tony -----------------------------------------From: "R B" To: gtk...@li... Cc: Sent: Wednesday January 30 2019 8:11:12PM Subject: Re: [Gtkwave-users] vcd2lxt2 performance writing to NFS disk (fseek & zlib) Using vcd2lxt2 --checkpoint=1my 300M vcd test case runs faster and produces a smaller lxt2 file. What are the downsides to that? Are results data-dependent (sometimes slower & larger)?Thanks,-Sto |