describe plots
This commit is contained in:
parent
fb31e44f00
commit
5adc7baf24
2 changed files with 8 additions and 1 deletions
|
@ -332,8 +332,15 @@ The conclusion is similar to FETCH: while these commands are OK to be slow, it's
|
||||||
|
|
||||||
### Listing mailboxes
|
### Listing mailboxes
|
||||||
|
|
||||||
|
Another object that can be queried in IMAP are mailboxes, through the LIST command.
|
||||||
|
The test consists of 1) LOGIN, 2) LIST, and 3) LOGOUT done on a user account with 5 mailboxes.
|
||||||
|
|
||||||
![List mailboxes](list.png)
|
![List mailboxes](list.png)
|
||||||
|
|
||||||
|
There are only 2 spikes (LOGIN and LOGOUT), as the mailbox list is loaded eagerly when the user connects.
|
||||||
|
Because it's a small datastructure, it's quick to parse it, which explains why there is no CPU/memory spike
|
||||||
|
for the LIST command in itself.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Discussion
|
## Discussion
|
||||||
|
|
|
@ -184,7 +184,7 @@
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
<p>
|
<p>
|
||||||
<a class="text-aerogramme-blue underline" href="/documentation/design/related-work/">Read our related work analysis</a>
|
<a class="text-aerogramme-blue underline" href="/documentation/internals/related-work/">Read our related work analysis</a>
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
Loading…
Reference in a new issue