search

JuliaDataCubes / YAXArrays.jl

Yet Another XArray-like Julia package
https://juliadatacubes.github.io/YAXArrays.jl/
Other
99 stars 16 forks source link

Revert "Lina slices table" #275

Closed lazarusA closed 1 year ago

lazarusA commented 1 year ago

Reverts JuliaDataCubes/YAXArrays.jl#274

github-actions[bot] commented 1 year ago
Benchmark result # Judge result # Benchmark Report for */home/runner/work/YAXArrays.jl/YAXArrays.jl* ## Job Properties * Time of benchmarks: - Target: 1 Jul 2023 - 10:56 - Baseline: 1 Jul 2023 - 10:56 * Package commits: - Target: df6c6f - Baseline: fa679c * Julia commits: - Target: 147bdf - Baseline: 147bdf * Julia command flags: - Target: None - Baseline: None * Environment variables: - Target: None - Baseline: None ## Results A ratio greater than `1.0` denotes a possible regression (marked with :x:), while a ratio less than `1.0` denotes a possible improvement (marked with :white_check_mark:). Only significant results - results that indicate possible regressions or improvements - are shown below (thus, an empty table means that all benchmark results remained invariant between builds). | ID | time ratio | memory ratio | |--------------------------|------------------------------|------------------------------| | `["mapslices", "small"]` | 0.03 (5%) :white_check_mark: | 0.23 (1%) :white_check_mark: | ## Benchmark Group List Here's a list of all the benchmark groups executed by this job: - `["mapslices"]` ## Julia versioninfo ### Target ``` Julia Version 1.9.1 Commit 147bdf428cd (2023-06-07 08:27 UTC) Platform Info: OS: Linux (x86_64-linux-gnu) Ubuntu 22.04.2 LTS uname: Linux 5.15.0-1040-azure #47-Ubuntu SMP Thu Jun 1 19:38:24 UTC 2023 x86_64 x86_64 CPU: Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz: speed user nice sys idle irq #1 2095 MHz 1335 s 0 s 211 s 1126 s 0 s #2 2095 MHz 1050 s 0 s 200 s 1407 s 0 s Memory: 6.769481658935547 GB (4959.3203125 MB free) Uptime: 272.75 sec Load Avg: 1.51 0.93 0.39 WORD_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-14.0.6 (ORCJIT, skylake-avx512) Threads: 1 on 2 virtual cores ``` ### Baseline ``` Julia Version 1.9.1 Commit 147bdf428cd (2023-06-07 08:27 UTC) Platform Info: OS: Linux (x86_64-linux-gnu) Ubuntu 22.04.2 LTS uname: Linux 5.15.0-1040-azure #47-Ubuntu SMP Thu Jun 1 19:38:24 UTC 2023 x86_64 x86_64 CPU: Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz: speed user nice sys idle irq #1 2095 MHz 1369 s 0 s 213 s 1412 s 0 s #2 2095 MHz 1340 s 0 s 206 s 1435 s 0 s Memory: 6.769481658935547 GB (5001.4921875 MB free) Uptime: 305.06 sec Load Avg: 1.31 0.93 0.41 WORD_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-14.0.6 (ORCJIT, skylake-avx512) Threads: 1 on 2 virtual cores ``` --- # Target result # Benchmark Report for */home/runner/work/YAXArrays.jl/YAXArrays.jl* ## Job Properties * Time of benchmark: 1 Jul 2023 - 10:56 * Package commit: df6c6f * Julia commit: 147bdf * Julia command flags: None * Environment variables: None ## Results Below is a table of this job's results, obtained by running the benchmarks. The values listed in the `ID` column have the structure `[parent_group, child_group, ..., key]`, and can be used to index into the BaseBenchmarks suite to retrieve the corresponding benchmarks. The percentages accompanying time and memory values in the below table are noise tolerances. The "true" time/memory value for a given benchmark is expected to fall within this percentage of the reported value. An empty cell means that the value was zero. | ID | time | GC time | memory | allocations | |--------------------------|----------------:|-----------:|----------------:|------------:| | `["mapslices", "small"]` | 400.647 ms (5%) | 199.891 ms | 325.11 MiB (1%) | 41610 | ## Benchmark Group List Here's a list of all the benchmark groups executed by this job: - `["mapslices"]` ## Julia versioninfo ``` Julia Version 1.9.1 Commit 147bdf428cd (2023-06-07 08:27 UTC) Platform Info: OS: Linux (x86_64-linux-gnu) Ubuntu 22.04.2 LTS uname: Linux 5.15.0-1040-azure #47-Ubuntu SMP Thu Jun 1 19:38:24 UTC 2023 x86_64 x86_64 CPU: Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz: speed user nice sys idle irq #1 2095 MHz 1335 s 0 s 211 s 1126 s 0 s #2 2095 MHz 1050 s 0 s 200 s 1407 s 0 s Memory: 6.769481658935547 GB (4959.3203125 MB free) Uptime: 272.75 sec Load Avg: 1.51 0.93 0.39 WORD_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-14.0.6 (ORCJIT, skylake-avx512) Threads: 1 on 2 virtual cores ``` --- # Baseline result # Benchmark Report for */home/runner/work/YAXArrays.jl/YAXArrays.jl* ## Job Properties * Time of benchmark: 1 Jul 2023 - 10:56 * Package commit: fa679c * Julia commit: 147bdf * Julia command flags: None * Environment variables: None ## Results Below is a table of this job's results, obtained by running the benchmarks. The values listed in the `ID` column have the structure `[parent_group, child_group, ..., key]`, and can be used to index into the BaseBenchmarks suite to retrieve the corresponding benchmarks. The percentages accompanying time and memory values in the below table are noise tolerances. The "true" time/memory value for a given benchmark is expected to fall within this percentage of the reported value. An empty cell means that the value was zero. | ID | time | GC time | memory | allocations | |--------------------------|--------------:|-----------:|--------------:|------------:| | `["mapslices", "small"]` | 15.327 s (5%) | 624.681 ms | 1.38 GiB (1%) | 18498963 | ## Benchmark Group List Here's a list of all the benchmark groups executed by this job: - `["mapslices"]` ## Julia versioninfo ``` Julia Version 1.9.1 Commit 147bdf428cd (2023-06-07 08:27 UTC) Platform Info: OS: Linux (x86_64-linux-gnu) Ubuntu 22.04.2 LTS uname: Linux 5.15.0-1040-azure #47-Ubuntu SMP Thu Jun 1 19:38:24 UTC 2023 x86_64 x86_64 CPU: Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz: speed user nice sys idle irq #1 2095 MHz 1369 s 0 s 213 s 1412 s 0 s #2 2095 MHz 1340 s 0 s 206 s 1435 s 0 s Memory: 6.769481658935547 GB (5001.4921875 MB free) Uptime: 305.06 sec Load Avg: 1.31 0.93 0.41 WORD_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-14.0.6 (ORCJIT, skylake-avx512) Threads: 1 on 2 virtual cores ``` --- # Runtime information | Runtime Info | | |:--|:--| | BLAS #threads | 1 | | `BLAS.vendor()` | `lbt` | | `Sys.CPU_THREADS` | 2 | `lscpu` output: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: GenuineIntel Model name: Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz CPU family: 6 Model: 85 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping: 4 BogoMIPS: 4190.39 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 cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f avx512dq rdseed adx smap clflushopt avx512cd avx512bw avx512vl xsaveopt xsavec xsaves md_clear Hypervisor vendor: Microsoft Virtualization type: full L1d cache: 64 KiB (2 instances) L1i cache: 64 KiB (2 instances) L2 cache: 2 MiB (2 instances) L3 cache: 35.8 MiB (1 instance) NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerability Itlb multihit: KVM: Mitigation: VMX unsupported Vulnerability L1tf: Mitigation; PTE Inversion Vulnerability Mds: Mitigation; Clear CPU buffers; SMT Host state unknown Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown Vulnerability Retbleed: Vulnerable Vulnerability Spec store bypass: Vulnerable Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT Host state unknown | Cpu Property | Value | |:------------------ |:------------------------------------------------------- | | Brand | Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz | | Vendor | :Intel | | Architecture | :Skylake | | Model | Family: 0x06, Model: 0x55, Stepping: 0x04, Type: 0x00 | | Cores | 2 physical cores, 2 logical cores (on executing CPU) | | | No Hyperthreading hardware capability detected | | Clock Frequencies | Not supported by CPU | | Data Cache | Level 1:3 : (32, 1024, 36608) kbytes | | | 64 byte cache line size | | Address Size | 48 bits virtual, 46 bits physical | | SIMD | 512 bit = 64 byte max. SIMD vector size | | Time Stamp Counter | TSC is accessible via `rdtsc` | | | TSC increased at every clock cycle (non-invariant TSC) | | Perf. Monitoring | Performance Monitoring Counters (PMC) are not supported | | Hypervisor | Yes, Microsoft |
github-actions[bot] commented 1 year ago

Pull Request Test Coverage Report for Build 5430650331

Totals Coverage Status
Change from base Build 5430604828: 0.0%
Covered Lines: 1353
Relevant Lines: 1785
💛 - Coveralls
codecov[bot] commented 1 year ago

Codecov Report

Patch and project coverage have no change.

Comparison is base (fa679c3) 75.82% compared to head (e429c2b) 75.82%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #275 +/- ## ======================================= Coverage 75.82% 75.82% ======================================= Files 12 12 Lines 1853 1853 ======================================= Hits 1405 1405 Misses 448 448 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

meggart commented 1 year ago

Could you quickly give a reasoning why the cubefittable exaple is not fitting for this section?

meggart commented 1 year ago

I know there must be a reason, just for me to understand

lazarusA commented 1 year ago

@meggart this is already merged https://github.com/JuliaDataCubes/YAXArrays.jl/pull/274. Apologies for the confusion. Is just that the build was not successful, but this is an issue with conda and python. Hence, that's why you don't see the example live in the docs, but it is there. Once I have a chance I will try to figured out what's going on with conda and pycall in CI.