[ { "path": "table_paper/2407.00013v1.json", "table_id": "1", "section": "4.1", "all_context": [ "In this subsection, the performance of the caching system is evaluated in terms of cache hit and cache miss ratios, with the key variable being the threshold value set for the “sliding window algorithm”, which means after the threshold is reached, the IoT data corresponding to the context attribute will be considered as stale and evicted from cache.", "The threshold is systematically varied from 10 minutes to 25 minutes, in increments of 5 minutes, as indicated in Table 1 .", "The results of this variation, visualized in Figure 4 , suggest a trend of increasing cache hits as the threshold value rises.", "After analysis, a 20-minute threshold has been selected for the experiments conducted in the subsequent sections.", "It s important to note that post a threshold of 22 minutes, no significant impact or changes were observed in the system s performance.", "This threshold selection ensures an optimal balance between cached context freshness and computational efficiency.", "" ], "target_context_ids": [ 0, 1, 2, 3, 4, 5 ], "selected_paragraphs": [ "[paragraph id = 0] In this subsection, the performance of the caching system is evaluated in terms of cache hit and cache miss ratios, with the key variable being the threshold value set for the “sliding window algorithm”, which means after the threshold is reached, the IoT data corresponding to the context attribute will be considered as stale and evicted from cache.", "[paragraph id = 1] The threshold is systematically varied from 10 minutes to 25 minutes, in increments of 5 minutes, as indicated in Table 1 .", "[paragraph id = 2] The results of this variation, visualized in Figure 4 , suggest a trend of increasing cache hits as the threshold value rises.", "[paragraph id = 3] After analysis, a 20-minute threshold has been selected for the experiments conducted in the subsequent sections.", "[paragraph id = 4] It s important to note that post a threshold of 22 minutes, no significant impact or changes were observed in the system s performance.", "[paragraph id = 5] This threshold selection ensures an optimal balance between cached context freshness and computational efficiency." ], "table_html": "
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ThresholdValue
10152025
Cache hit174179184186
Cache miss26211614
Ratio6.78.511.513.3
\n
Table 1: Cache hit and cache miss ratios at different thresholds.
\n
", "perturb_sentence_id": 1, "output": { "perturbed_statement": "[paragraph id = 1] The threshold is systematically varied from 15 minutes to 30 minutes, in increments of 5 minutes, as indicated in Table 1. The results of this variation, visualized in Figure 4, suggest a trend of decreasing cache hits as the threshold value rises.", "perturbed_explanation": "1. The original statement accurately describes the range of variation for the threshold, which is from 10 minutes to 25 minutes, and the observed trend of cache hits increasing with the threshold value, supported by visual references in the table and figure.\n2. The statement is inaccurate because it alters the threshold range to 15–30 minutes, which is not the analyzed range, and misrepresents the trend by claiming a decrease in cache hits rather than an increase. Therefore, this statement contradicts the data analysis results provided." } }, { "path": "table_paper/2407.00013v1.json", "table_id": "2", "section": "4.2", "all_context": [ "In this subsection, the size of the incoming entries load was systematically varied, testing with 150, 250, 350, and 500 for each threshold from 10 to 25 minutes in increments of 5 minutes as shown in Table 2 .", "The findings reveal a consistent pattern across all test cases.", "With an increasing number of entries, both cache hit and cache miss counts increase, but the cache hit ratio remains relatively consistent indicating that the “hybrid approach” also supports scalability.", "From the Cache Hit Ratio heatmap (Figure 5 ), we can observe a pattern of increasing cache hit ratio with an increasing threshold for all entry sets.", "For a threshold of 10, the cache hit ratio remains relatively steady around 7.33 to 7.36 across all entries.", "As the threshold increases to 15, there is a notable improvement in the ratio, reaching up to 9.47 for 500 entries.", "When the threshold is increased further to 20 minutes, the ratio experiences an additional boost to a range of approximately 12.33 to 12.46.", "Interestingly, upon reaching a 25-minute threshold, the ratio increases to around 14.38 for all query sets, except for 250 queries where it marginally drops to 14.15.", "This discrepancy could be attributed to various factors including caching policies, size of the cache, or variability in the access patterns.", "These findings, illustrated in the heatmap, affirm the choice of a 20-minute threshold as a suitable point.", "While the cache hit ratio generally improves with an increase in threshold, the gains beyond the 20-minute mark are relatively minor.", "This confirms the trade-off between context freshness and computational efficiency, and indicates the diminishing returns of increasing the threshold beyond 20 minutes.", "Therefore, a 20-minute threshold appears to be the optimal point for maintaining an efficient cache system, given the current configuration and workload.", "" ], "target_context_ids": [ 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 ], "selected_paragraphs": [ "[paragraph id = 0] In this subsection, the size of the incoming entries load was systematically varied, testing with 150, 250, 350, and 500 for each threshold from 10 to 25 minutes in increments of 5 minutes as shown in Table 2 .", "[paragraph id = 2] With an increasing number of entries, both cache hit and cache miss counts increase, but the cache hit ratio remains relatively consistent indicating that the “hybrid approach” also supports scalability.", "[paragraph id = 3] From the Cache Hit Ratio heatmap (Figure 5 ), we can observe a pattern of increasing cache hit ratio with an increasing threshold for all entry sets.", "[paragraph id = 4] For a threshold of 10, the cache hit ratio remains relatively steady around 7.33 to 7.36 across all entries.", "[paragraph id = 5] As the threshold increases to 15, there is a notable improvement in the ratio, reaching up to 9.47 for 500 entries.", "[paragraph id = 6] When the threshold is increased further to 20 minutes, the ratio experiences an additional boost to a range of approximately 12.33 to 12.46.", "[paragraph id = 7] Interestingly, upon reaching a 25-minute threshold, the ratio increases to around 14.38 for all query sets, except for 250 queries where it marginally drops to 14.15.", "[paragraph id = 8] This discrepancy could be attributed to various factors including caching policies, size of the cache, or variability in the access patterns.", "[paragraph id = 9] These findings, illustrated in the heatmap, affirm the choice of a 20-minute threshold as a suitable point.", "[paragraph id = 10] While the cache hit ratio generally improves with an increase in threshold, the gains beyond the 20-minute mark are relatively minor.", "[paragraph id = 11] This confirms the trade-off between context freshness and computational efficiency, and indicates the diminishing returns of increasing the threshold beyond 20 minutes.", "[paragraph id = 12] Therefore, a 20-minute threshold appears to be the optimal point for maintaining an efficient cache system, given the current configuration and workload." ], "table_html": "
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
No. of queriesThresholdCache HitCache missCache Hit Ratio
15010528727.33
15542589.34
205554512.33
255613914.38
250108801207.33
15904969.41
209257512.33
259346614.15
3501012321687.33
1512661349.44
20129610412.46
2513099114.38
5001017612397.36
1518091919.47
20185114912.42
25187013014.38
\n
Table 2: Cache hit and cache miss ratios at different number of entries.
\n
", "perturb_sentence_id": 0, "output": { "perturbed_statement": "[paragraph id = 0] In this subsection, the size of the incoming entries load was systematically varied, testing with 200, 250, 350, and 600 for each threshold from 10 to 25 minutes in increments of 5 minutes as shown in Table 2. The findings reveal a consistent pattern across all test cases.", "perturbed_explanation": "1. The original explanation highlights the systematic variation in the size of the incoming entries load to specific values: 150, 250, 350, and 500 entries. 2. The statement introduces different entry load sizes (200 and 600 instead of 150 and 500), which conflicts with the identified tested values. This alteration affects the understanding of the experimental setup and its methodology." } } ]