You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON encoding of sonar ps data on a Fox login node is nearly 40% smaller than the CSV encoding (b/c records do not carry redundant version, timestamp and hostname for every record, and b/c the hostname is fairly long on the login node). When I looked at these data the other day I got this reversed: I thought the CSV was smaller.
Obviously if we really care about data size we'll use some binary encoding or make sure that data are compressed somehow for transmission, ideally very cheaply.
The text was updated successfully, but these errors were encountered:
The JSON encoding of sonar ps data on a Fox login node is nearly 40% smaller than the CSV encoding (b/c records do not carry redundant version, timestamp and hostname for every record, and b/c the hostname is fairly long on the login node). When I looked at these data the other day I got this reversed: I thought the CSV was smaller.
Obviously if we really care about data size we'll use some binary encoding or make sure that data are compressed somehow for transmission, ideally very cheaply.
The text was updated successfully, but these errors were encountered: