[LU-14532] sanity test_123ac: FAIL: statx --cached=always -D 100000 files is slower with statahead! Created: 17/Mar/21  Updated: 14/Dec/23  Resolved: 14/Dec/23

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.14.0, Lustre 2.15.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by LU-15623 sanity: test_123ac: statx -c %n %i %A... Resolved
Related
is related to LU-14104 sanity/123* FAIL: statx -l ... files ... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for jianyu <yujian@whamcloud.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/322e367d-63f0-474b-b32f-c98740c8720e

test_123ac failed with the following error:

llite.lustre-ffff984843c68000.statahead_max=0
100000

real	0m0.160s
user	0m0.013s
sys	0m0.050s
statx --cached=always -D 100000 files without statahead: 1 sec
llite.lustre-ffff984843c68000.statahead_max=32
32
100000

real	0m8.003s
user	0m0.007s
sys	0m0.050s
statx --cached=always -D 100000 files with statahead: 8 sec
statahead total: 13
statahead wrong: 0
agl total: 10
llite.lustre-ffff984843c68000.statahead_max=0
100000

real	0m0.147s
user	0m0.008s
sys	0m0.045s
statx --cached=always -D 100000 files again without statahead: 0 sec
llite.lustre-ffff984843c68000.statahead_max=32
 sanity test_123ac: @@@@@@ FAIL: statx --cached=always -D 100000 files is slower with statahead! 

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_123ac - statx --cached=always -D 100000 files is slower with statahead!



 Comments   
Comment by Sebastien Buisson [ 17/Sep/21 ]

+1 on master:
https://testing.whamcloud.com/test_sets/68a4d2dd-9eec-49ba-9963-f236c1d05a4b

Comment by Xing Huang [ 14/Dec/22 ]

+1 on master:
https://testing.whamcloud.com/test_sets/57133f0c-eb40-41e9-836a-2cba68197951
and detail in:
https://testing.whamcloud.com/test_logs/11bfa601-bf05-48a2-bb50-59ef6796dc6c/show_text

Comment by Dongyang Li [ 15/Jan/23 ]

Looks like been fixed by LU-14104

Generated at Sat Feb 10 03:10:34 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.