# Technical Working Group: Scalability & Performance **URL:** \ **Category:** Developers\ **Tags:** Discussing, community-consideration\ **Created:** [July 11, 2022, 9:51am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265 "2022-07-11T09:51:10Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [October 20, 2022, 6:51am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/22 "2022-10-20T06:51:15Z")
Reminder: Later **today, at 5:30 pm CEST** , we’ll have a discussion on Inter Canister Query Calls and the recent [Composite Queries Proposal](https://forum.dfinity.org/t/proposal-composite-queries/15979) I’m looking forward to an interesting session! ---
**Author:** ![paulyoung](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/paulyoung/32/5251_2.png) [@paulyoung](https://forum.dfinity.org/u/paulyoung)\ **Post date:** [October 20, 2022, 2:36pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/23 "2022-10-20T14:36:59Z")
I won’t be able to make it today due to the meetup in LA. I think a couple of other people will be there as well. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [October 21, 2022, 7:44am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/24 "2022-10-21T07:44:55Z")
[Link to slides](https://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE/edit?usp=sharing) and [recording](https://dfinity.zoom.us/rec/share/H5bbsNwkG2tf1Xx3uILbyzhzPWm-pxRjzFExD--KVHAsXN4akjTO-dwpFmjX0Oaa.Nx5Wtsg8JVg_jXL7) of the session on Inter-canister query calls. ---
**Author:** ![JaMarco](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamarco/32/7629_2.png) [@JaMarco](https://forum.dfinity.org/u/JaMarco)\ **Post date:** [October 21, 2022, 5:21pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/25 "2022-10-21T17:21:47Z")
How can I view the recording? It says I cannot view the recording because I have no permission. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [October 22, 2022, 3:19pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/26 "2022-10-22T15:19:26Z")
Please try again. I got the permissions wrong. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [November 16, 2022, 1:01pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/27 "2022-11-16T13:01:48Z")
**Tomorrow 11/17 at 5:30pm CET** , the next WG session will happen. The main topic we’d like to discuss in this session is [Improving the utility of stable memory](https://forum.dfinity.org/t/improving-the-utility-of-stable-memory/16210). Please read the forum post in advance and think about the questions raised. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [November 18, 2022, 10:15am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/28 "2022-11-18T10:15:37Z")
@johan couldn’t join the session, so we had a free discussion on stable memory on the IC. [Updated Meeting Notes](https://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE/edit?usp=sharing) and [Recording](https://dfinity.zoom.us/rec/share/hNvy_iT9leCFYf6pm2-BsbIex5PBGzE51e0_ZKV3kchocDUZUdJbgCq7Vu6ulqLo.jUpm-o80A9IZqS09). ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [December 14, 2022, 10:19am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/29 "2022-12-14T10:19:17Z")
We’ll skip this week’s Scalability & Performance WG. I already wish you a nice Christmas and see you all in January. ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [December 16, 2022, 2:52pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/30 "2022-12-16T14:52:38Z")
I’d like to follow-up on this question. Will multiple memories do anything that would make stable structures unnecessary? ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [December 16, 2022, 2:59pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/31 "2022-12-16T14:59:39Z")
To specify my question more, will it be possible to create a native data structure (like a Rust struct) and simply tell it which memory to use during instantiation of the data structure? And could one or more memories be set aside as stable, so that we could actually have native stable data structures instead of having to create specialized (and a bit limited) stable data structures? I’m imagining the main Wasm heap could maintain pointers to native structures in the stable memories, and perhaps on upgrade those pointers can be collected and stored in a stable memory, and then restored to their variables after upgrade. Is this just crazy talk? @johan @rossberg ---
**Author:** ![ulan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/ulan/32/2705_2.png) [@ulan](https://forum.dfinity.org/u/ulan)\ **Post date:** [December 16, 2022, 4:16pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/32 "2022-12-16T16:16:23Z")
The memory layout of a native data structure is not guaranteed to be stable or backwards compatible. In theory, even if the developer uses the same compiler binary with the same source code, the compiler is still allowed to use a different memory layout of native data structures based on non-deterministic optimizations. While multi-memories enable fast access to the stable memory, the developer still needs to ensure that data stored in the stable memory is stable and backwards compatible. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [January 18, 2023, 4:54pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/33 "2023-01-18T16:54:44Z")
Hey everybody, **Tomorrow 01/19 at 5:30pm CET** we’ll have the first WG session of 2023. The main topic for tomorrow will be a discussion on: _Canister queues (ingress, input and output) overview and case studies of handling large message volumes_ led by @dsarlis. Looking forward to see many of you! ---
**Author:** ![dymayday](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dymayday/32/4935_2.png) [@dymayday](https://forum.dfinity.org/u/dymayday)\ **Post date:** [January 18, 2023, 7:35pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/34 "2023-01-18T19:35:00Z")
Unfortunately I could not attend this meeting for family reasons. Would you happen to have a recording to share @domwoe please ? ---
**Author:** ![dsarlis](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dsarlis/32/689_2.png) [@dsarlis](https://forum.dfinity.org/u/dsarlis)\ **Post date:** [January 19, 2023, 9:00am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/35 "2023-01-19T09:00:28Z")
The meeting is actually scheduled for today the 19th (I guess Dominic made a typo on the date that no one noticed 😅). ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [January 19, 2023, 9:04am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/36 "2023-01-19T09:04:08Z")
> [@dsarlis](#): > > The meeting is actually scheduled for today the 19th (I guess Dominic made a typo on the date that no one noticed 😅). Oopsie, fixed. > [@dymayday](#): > > Unfortunately I could not attend this meeting for family reasons. Would you happen to have a recording to share @domwoe please ? In any case, I always record and share. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [January 19, 2023, 8:14pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/37 "2023-01-19T20:14:39Z")
Updated [meeting notes](https://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE/edit?usp=sharing) and [recording](https://dfinity.zoom.us/rec/share/1WQ4WPb-33-_0lZtl_LgqFv06MdPOyrc632NTGSkG98Ajq0kSHCiWIlCKtAcHqBR.SBOnCahfe_KfbbTi). ---
**Author:** ![Samer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/samer/32/8943_2.png) [@Samer](https://forum.dfinity.org/u/Samer)\ **Post date:** [January 21, 2023, 11:16am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/38 "2023-01-21T11:16:06Z")
Will the recording be uploaded to youtube? Zoom player acting buggy on my side ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [January 21, 2023, 7:51pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/39 "2023-01-21T19:51:47Z")
> [@Samer](#): > > Will the recording be uploaded to youtube? hmm, we haven’t uploaded WG sessions to Youtube thus far. I don’t think there’s a particular blocker but the audience is pretty small at the moment. ---
**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\ **Post date:** [January 21, 2023, 10:07pm UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/40 "2023-01-21T22:07:11Z")
This would be a great bounty for someone to pursue while exploring these patterns at the library level. Pipelineify already handles a lot of this queuing action, and it would likely need to use some of the libraries that would help with managing input output queues. > [@Awarded: ICDevs.org Bounty #43 - Pipelinify Updates - $4,000](https://forum.dfinity.org/t/open-icdevs-org-bounty-43-pipelinify-updates-4-000/17918): > > Pipelinify Updates - Motoko - #43 Current Status: Discussion Discussion (01/09/2023) Ratification: (01/09/2023) Open for application: (01/09/2023) Assigned In Review Closed [Official Link](https://icdevs.org/bounties/2023/01/09/43-Pipelinify-Updates-Motoko.html)Bounty Details Bounty Amount: $4,000 USD of ICP at award date. [ICDevs.org](http://ICDevs.org) Bounty Acceleration: For each 1 ICP sent to 269b560f921487247b75d5507c9af250af3a932c372111fa5fbb66eba64354c5, [ICDevs.org](http://ICDevs.org) will add .25 ICP to this issue and .75 ICP to fund other [ICDevs.org](http://ICDevs.org) initiatives. Project Type: Individual Opened: … ---
**Author:** ![blabagastered](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/blabagastered/32/8592_2.png) [@blabagastered](https://forum.dfinity.org/u/blabagastered)\ **Post date:** [January 22, 2023, 1:12am UTC](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265/41 "2023-01-22T01:12:53Z")
I remember reading about throughput limitations of BTC transactions, but can’t find it. Something like one transaction per block per subnet. Does anyone know the actual number and whether there is ongoing work to increase it? Found it: > [@Exploring the Potential of Zero-Knowledge Rollups (ZKR) for Improved Cross-chain Efficiency on the IC](https://forum.dfinity.org/t/exploring-the-potential-of-zero-knowledge-rollups-zkr-for-improved-cross-chain-efficiency-on-the-ic/17767/1): > > there is a limit of 1 txn/second per subnet [Previous page](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265.md?page=1) [Next page](https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265.md?page=3)