High CPU usage compared to watch equivalent

[xfzv]

Not sure whether this behaves correctly or doesn't so I thought a discussion would be more appropriate for now.

I've been playing around with v1.0.0 and v1.0.1 and on a server with limited resources (2 cores, 4 GB of RAM).

% watch -n 10 `my command`

---

% viddy -n 10 `my command`

The CPU consumption is constant for both commands. I tried other commands and it seems that the more output lines the command produces, the higher the CPU usage.

With another command that produces less output:

% watch -n 10 `my command`

---

% viddy -n 10 `my command`

Note that watch consumes the same amount of CPU/RAM for both commands.

viddy CPU usage for the first command is really high, so much that I'm sticking with watch for now.

Is anyone observing similar resource usage? Just curious.

[sachaos]

@xfzv Thank you for the feedback.
Yes, Viddy is heavier than Watch because it offers rich features, especially the pager functionality. However, there is potential for optimizing this feature in the future.

[xfzv]

I see. Thanks for the reply!