# Fluid.bufnoveltyslice~ and the 'transbuf'

**URL:** <https://discourse.flucoma.org/t/fluid-bufnoveltyslice-and-the-transbuf/130>\
**Category:** Usage Questions\
**Created:** [December 9, 2018, 4:17pm UTC](https://discourse.flucoma.org/t/fluid-bufnoveltyslice-and-the-transbuf/130 "2018-12-09T16:17:40Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [May 26, 2019, 7:50pm UTC](https://discourse.flucoma.org/t/fluid-bufnoveltyslice-and-the-transbuf/130/16 "2019-05-26T19:50:26Z")

</div>

Hehe, they are legible, but too slow really, for big data. Did lots of testing for the update of C-C-Combine and coll/text was the way to go, by a significant margin, in terms of speed.

So not really sure what’s best, but I do have “architecture” on the brain from [the other thread](https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205/11), and was reminded of this.

For me, all my concerns about buffers still holds up in that it lacks context/meaning, and importantly, dimensional scalability. And in playing with it “in context” in [the other thread](https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205/11), I can see having to go in and out of buffers constantly adding a significant overhead to everyday processing.

---

_[View the full topic](https://discourse.flucoma.org/t/fluid-bufnoveltyslice-and-the-transbuf/130)._