What is the computation Power of Matlab Online?

Simple question in the title - what is the computation power of Matlab Online?

There exist another question with the same title, however the provided answer has nothing to do with the question.

Does anyone has an idea?

[Muhammad Shiraz Ahmad Ahmad]

In Windows system

system('systeminfo')

For my case, matlab online was runing on linux, so here are some details (matlab commands and outputs):

system('lscpu')

Architecture: x86_64

CPU op-mode(s): 32-bit, 64-bit

Byte Order: Little Endian

CPU(s): 16

On-line CPU(s) list: 0-15

Thread(s) per core: 2

Core(s) per socket: 8

Socket(s): 1

NUMA node(s): 1

Vendor ID: GenuineIntel

CPU family: 6

Model: 85

Model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz

Stepping: 7

CPU MHz: 3099.855

BogoMIPS: 4999.99

Hypervisor vendor: KVM

Virtualization type: full

L1d cache: 32K

L1i cache: 32K

L2 cache: 1024K

L3 cache: 36608K

NUMA node0 CPU(s): 0-15

Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke

system('lsblk')

lsblk: dm-20: failed to get device path

lsblk: dm-1: failed to get device path

lsblk: dm-10: failed to get device path

lsblk: dm-29: failed to get device path

lsblk: dm-19: failed to get device path

lsblk: dm-27: failed to get device path

lsblk: dm-8: failed to get device path

lsblk: dm-17: failed to get device path

lsblk: dm-25: failed to get device path

lsblk: dm-6: failed to get device path

lsblk: dm-15: failed to get device path

lsblk: dm-23: failed to get device path

lsblk: dm-4: failed to get device path

lsblk: dm-13: failed to get device path

lsblk: dm-20: failed to get device path

lsblk: dm-1: failed to get device path

lsblk: dm-10: failed to get device path

lsblk: dm-29: failed to get device path

lsblk: dm-19: failed to get device path

lsblk: dm-27: failed to get device path

lsblk: dm-8: failed to get device path

lsblk: dm-17: failed to get device path

lsblk: dm-25: failed to get device path

lsblk: dm-6: failed to get device path

lsblk: dm-15: failed to get device path

lsblk: dm-23: failed to get device path

lsblk: dm-4: failed to get device path

lsblk: dm-13: failed to get device path

lsblk: dm-21: failed to get device path

lsblk: dm-2: failed to get device path

lsblk: dm-11: failed to get device path

lsblk: dm-0: failed to get device path

lsblk: dm-28: failed to get device path

lsblk: dm-9: failed to get device path

lsblk: dm-18: failed to get device path

lsblk: dm-26: failed to get device path

lsblk: dm-7: failed to get device path

lsblk: dm-16: failed to get device path

lsblk: dm-24: failed to get device path

lsblk: dm-5: failed to get device path

lsblk: dm-14: failed to get device path

lsblk: dm-22: failed to get device path

lsblk: dm-3: failed to get device path

lsblk: dm-12: failed to get device path

lsblk: dm-21: failed to get device path

lsblk: dm-2: failed to get device path

lsblk: dm-11: failed to get device path

lsblk: dm-0: failed to get device path

lsblk: dm-28: failed to get device path

lsblk: dm-9: failed to get device path

lsblk: dm-18: failed to get device path

lsblk: dm-26: failed to get device path

lsblk: dm-7: failed to get device path

lsblk: dm-16: failed to get device path

lsblk: dm-24: failed to get device path

lsblk: dm-5: failed to get device path

lsblk: dm-14: failed to get device path

lsblk: dm-22: failed to get device path

lsblk: dm-3: failed to get device path

lsblk: dm-12: failed to get device path

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

nvme0n1 259:2 0 20G 0 disk

└─nvme0n1p1 259:3 0 20G 0 part /etc/hosts

nvme2n1 259:1 0 320G 0 disk

nvme1n1 259:0 0 45G 0 disk /SupportPackages

system('df -H')

Filesystem Size Used Avail Use% Mounted on

overlay 21G 15G 5.1G 75% /

/dev/nvme0n1p1 21G 15G 5.1G 75% /etc/instance-userdata.conf

udev 67G 13k 67G 1% /proc/kcore

tmpfs 67G 0 67G 0% /proc/scsi

tmpfs 68M 0 68M 0% /dev

shm 68M 0 68M 0% /dev/shm

tmpfs 67G 0 67G 0% /sys/fs/cgroup

tmpfs 67G 0 67G 0% /sys/firmware

/dev/nvme1n1 48G 36G 9.1G 80% /MATLAB

/dev/mapper/vg_es-707b8f6508fc743f87b7ee908e73debb 11G 26M 9.9G 1% /tmp

tmpfs 269M 0 269M 0% /tmp/SESSION_CACHE

tmpfs 269M 0 269M 0% /.AddOnsUpper

unionfs-fuse 269M 0 269M 0% /.Add-Ons

system('mount | column -t')

overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay/e72281debb7bd52a20f0fbd6ad95b4833e8aa714c9786e26c8bd773019c3cd52/root,upperdir=/var/lib/docker/overlay/a866e628948efe4b7774c31de5b46964097c409c0756447a821a5e575361b1b5/upper,workdir=/var/lib/docker/overlay/a866e628948efe4b7774c31de5b46964097c409c0756447a821a5e575361b1b5/work)

/dev/nvme0n1p1 on /etc/instance-userdata.conf type ext4 (ro,relatime,discard,data=ordered)

/dev/nvme0n1p1 on /etc/resolv.conf type ext4 (rw,relatime,discard,data=ordered)

/dev/nvme0n1p1 on /etc/hostname type ext4 (rw,relatime,discard,data=ordered)

/dev/nvme0n1p1 on /etc/hosts type ext4 (rw,relatime,discard,data=ordered)

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)

proc on /proc/bus type proc (ro,relatime)

proc on /proc/fs type proc (ro,relatime)

proc on /proc/irq type proc (ro,relatime)

proc on /proc/sys type proc (ro,relatime)

proc on /proc/sysrq-trigger type proc (ro,relatime)

udev on /proc/kcore type devtmpfs (rw,nosuid,size=65230956k,nr_inodes=16307739,mode=755)

udev on /proc/timer_list type devtmpfs (rw,relatime,size=65230956k,nr_inodes=16307739,mode=755)

udev on /proc/sched_debug type devtmpfs (rw,relatime,size=65230956k,nr_inodes=16307739,mode=755)

tmpfs on /proc/scsi type tmpfs (ro,relatime)

tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)

mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)

shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)

sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,relatime,mode=755)

cgroup on /sys/fs/cgroup/cpuset type cgroup (ro,nosuid,nodev,noexec,relatime,cpuset)

cgroup on /sys/fs/cgroup/cpu type cgroup (ro,nosuid,nodev,noexec,relatime,cpu)

cgroup on /sys/fs/cgroup/cpuacct type cgroup (ro,nosuid,nodev,noexec,relatime,cpuacct)

cgroup on /sys/fs/cgroup/blkio type cgroup (ro,nosuid,nodev,noexec,relatime,blkio)

cgroup on /sys/fs/cgroup/memory type cgroup (ro,nosuid,nodev,noexec,relatime,memory)

cgroup on /sys/fs/cgroup/devices type cgroup (ro,nosuid,nodev,noexec,relatime,devices)

cgroup on /sys/fs/cgroup/freezer type cgroup (ro,nosuid,nodev,noexec,relatime,freezer)

cgroup on /sys/fs/cgroup/net_cls type cgroup (ro,nosuid,nodev,noexec,relatime,net_cls)

cgroup on /sys/fs/cgroup/perf_event type cgroup (ro,nosuid,nodev,noexec,relatime,perf_event)

cgroup on /sys/fs/cgroup/net_prio type cgroup (ro,nosuid,nodev,noexec,relatime,net_prio)

cgroup on /sys/fs/cgroup/hugetlb type cgroup (ro,nosuid,nodev,noexec,relatime,hugetlb)

cgroup on /sys/fs/cgroup/pids type cgroup (ro,nosuid,nodev,noexec,relatime,pids)

cgroup on /sys/fs/cgroup/rdma type cgroup (ro,nosuid,nodev,noexec,relatime,rdma)

systemd on /sys/fs/cgroup/systemd type cgroup (ro,nosuid,nodev,noexec,relatime,name=systemd)

tmpfs on /sys/firmware type tmpfs (ro,relatime)

/dev/nvme1n1 on /MATLAB type ext4 (ro,relatime,discard,data=ordered)

/dev/nvme1n1 on /SupportPackages type ext4 (ro,relatime,discard,data=ordered)

/dev/mapper/vg_es-707b8f6508fc743f87b7ee908e73debb on /tmp type ext4 (rw,relatime,data=ordered)

tmpfs on /tmp/SESSION_CACHE type tmpfs (rw,nosuid,nodev,noexec,relatime,size=262144k)

tmpfs on /.AddOnsUpper type tmpfs (rw,nosuid,nodev,noexec,relatime,size=262144k)

gds://(matlab_drive)/ on /MATLAB Drive type fuse.mwfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=8378,default_permissions,allow_other)

gds://(AddOns)/ on /.AddOnsLower type fuse.mwfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=8378,default_permissions,allow_other)

unionfs-fuse on /.Add-Ons type fuse.unionfs-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=8378,default_permissions,allow_other)

unionfs-fuse

system('free -m')

total used free shared buff/cache available

Mem: 127458 76246 40194 31 11017 48968

Swap: 0 0 0

Answer 1

[Nick Choi]

The following documentation pages should help give you a better idea of what tasks can be performed using MATLAB Online.

This documentation page provides an overview of the features and limitations of MATLAB Online:

https://www.mathworks.com/help/matlab-web/matlab/matlab_env/matlab-online.html

Additionally, this page provides a list of the supported toolboxes and any limitations associated with them:

https://www.mathworks.com/products/matlab-online/limitations.html

[Boris Blagov]

Thank you but this does not answer the question. It does not tell me anything about the computation power that is available (or its maximum) when I use the service.

Practically every user is allocated a given amount of hardware resources and for most single user licences this is probably the same.

[Philip Borghesani]

That's probably the best answer you are going to get. There are multiple types of systems used and they change over time. In addition MATLAB is running in a VM and other users of the same hardware may impact your performance.

The only real answer is try it yourself and see if the performance you get is good enough for your problem. In general it should not matter to you unless you have a very large problem.

Why do you care? If we knew that we might be able to give you an answer to any real problem/question like is it reasonable to use matlab online for this type of computing?

[Boris Blagov]

Thank you for your time, Philip.

This is a more acceptable answer. Also "we are not telling" is also as acceptable, but just putting links to unrelated things is not.

By the way, on the limitations part it is not mentioned that, depending on the product offering you may not run code longer than 295 seconds, which is a severe limitation.

Nevertheless at least some guidelines would have been nice, for example, there is most probably a maximum allocated memory (or a minimum), which is important when creating large matrices. If the amount of memory allocated to a user is variable, this would mean that a code might work on a day when not many other users are active and not on another. This would be imporant to know in advance for the code design. Some problems, even if not very computationally demanding simply require large matrices (such as Markov-Chain Monte Carlo methods).

In any case, thank you for the asnwer.