-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: single bracket querying of a graph (#1465) #1658
base: main
Are you sure you want to change the base?
Conversation
Current Aviator status
This pull request is currently open (not queued). How to mergeTo merge this PR, comment
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I see how duplicate i
and j
indexes add complexity to the new get_adjacency_submatrix()
routine. How about the following logic:
- we don't compute
unique()
- instead, we compute
adj_out <- adjacent_vertices(x, i, mode = "out")
ifi
is given, andadj_in <- adjacent_vertices(x, j, mode = "in")
ifj
is given - if none are given, we forward to a different existing routine
- if only one of
i
orj
is given, we're done - if both are given, we compute
vctrs::vec_set_intersect(adj_in, adj_out)
How is the test coverage for this code?
I'd appreciate it if all changes that do not rely on get_adjacency_submatrix()
came in one or several separate PRs. I'd like to do a few more iterations here.
d64b7b4
to
44561c5
Compare
Manipulating a graph via this logic was moved to #1661 |
I have tried this logic but always ran into issues for the case of non unique indices. |
f4795c7
to
56ba6e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get.adjacency.sparse()
with a directed graph should involve only one or two copies. We could use that result with regular matrix subsetting and then tweak for the directed case. While this is not ideal, it may well be faster than anything we can come up in R land. Further optimizations are then possible by adding a from
or to
argument to as_edgelist()
(which is called by get.adjacency.sparse()
).
I am surprised myself, but the difference between the submatrix routine and pkgload::load_all("~/git/R_packages/rigraph/")
#> ℹ Loading igraph
g <- sample_gnp(5000,0.05, directed = FALSE)
bench::mark(check = FALSE,
sub_sparse = get_adjacency_submatrix(g,1:100,sparse = TRUE),
sub_dense = get_adjacency_submatrix(g,1:100,sparse = FALSE),
full_sparse = as_adjacency_matrix(g,sparse = TRUE)[1:100,]
)
#> Warning: Some expressions had a GC in every iteration; so filtering is
#> disabled.
#> # A tibble: 3 × 6
#> expression min median `itr/sec` mem_alloc `gc/sec`
#> <bch:expr> <bch:tm> <bch:tm> <dbl> <bch:byt> <dbl>
#> 1 sub_sparse 2.01ms 2.13ms 401. 5.05MB 53.9
#> 2 sub_dense 2.22ms 2.44ms 299. 8.43MB 53.8
#> 3 full_sparse 31.91ms 33.76ms 22.9 105.47MB 66.8
g <- sample_gnp(5000,0.05, directed = TRUE)
bench::mark(check = FALSE,
sub_sparse = get_adjacency_submatrix(g,1:100,sparse = TRUE),
sub_dense = get_adjacency_submatrix(g,1:100,sparse = FALSE),
full_sparse = as_adjacency_matrix(g, sparse = TRUE)[1:100,]
)
#> Warning: Some expressions had a GC in every iteration; so filtering is
#> disabled.
#> # A tibble: 3 × 6
#> expression min median `itr/sec` mem_alloc `gc/sec`
#> <bch:expr> <bch:tm> <bch:tm> <dbl> <bch:byt> <dbl>
#> 1 sub_sparse 2.03ms 2.15ms 415. 3.97MB 24.0
#> 2 sub_dense 2.21ms 2.39ms 340. 7.79MB 45.8
#> 3 full_sparse 42.55ms 49.4ms 15.1 129.2MB 35.3 Created on 2025-01-23 with reprex v2.1.1 |
I am now convinced that this is as good as it gets. Any other approach seems to loose too mach performance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great progress, we're getting there!
Non unique i/j are now handled outside of |
This PR refactors single bracket querying of a graph (
g[1:3,4:6]
) ( #1465).[.igraph
In the old version, the complete adjacency matrix was computed and then a subset created. The refactored function now builds the submatrix directly. This leads to a little speedup and a lower memory footprint.
Created on 2025-01-18 with reprex v2.1.1