Skip to content
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

Segmentation Fault in Disk Mode Despite Fix in PR 147 #157

Open
griii opened this issue Mar 15, 2024 · 1 comment
Open

Segmentation Fault in Disk Mode Despite Fix in PR 147 #157

griii opened this issue Mar 15, 2024 · 1 comment
Labels
question Further information is requested

Comments

@griii
Copy link

griii commented Mar 15, 2024

I am reaching out to report an issue I am encountering with the marius_trian, specifically when using the disk mode. Despite the segmentation fault being addressed in this PR (#147), I am still experiencing the same problem after updating to the latest version of the project.

It is worth noting that the operation of Marius in memory mode is completely normal. Below are my configurations for Marius preprocessing.
图片

The following are my disk YAML configurations for marius_train.

# examples/configuration/ogbn_paper100m_disk.yaml
model:
  learning_task: NODE_CLASSIFICATION
  encoder:
    train_neighbor_sampling:
      - type: UNIFORM
        options:
          max_neighbors: 10
      - type: UNIFORM
        options:
          max_neighbors: 10
      - type: UNIFORM
        options:
          max_neighbors: 10
    layers:
      - - type: FEATURE
          output_dim: 100
      - - type: GNN
          options:
            type: GRAPH_SAGE
            aggregator: MEAN
          input_dim: 100
          output_dim: 256
          bias: true
      - - type: GNN
          options:
            type: GRAPH_SAGE
            aggregator: MEAN
          input_dim: 256
          output_dim: 256
          bias: true
      - - type: GNN
          options:
            type: GRAPH_SAGE
            aggregator: MEAN
          input_dim: 256
          output_dim: 150
          bias: true
  decoder:
    type: NODE
  loss:
    type: CROSS_ENTROPY
    options:
      reduction: SUM
  dense_optimizer:
    type: ADAM
    options:
      learning_rate: 0.01
storage:
  device_type: cuda
  dataset:
    dataset_dir: /data/wb2001/
  edges:
    type: FLAT_FILE
  nodes:
    type: HOST_MEMORY
  features:
    type: PARTITION_BUFFER
    options:
      num_partitions: 16
      buffer_capacity: 5
      prefetching: true
      fine_to_coarse_ratio: 1
      num_cache_partitions: 0
      node_partition_ordering: DISPERSED
  # prefetch: false
  # shuffle_input: true
  # full_graph_evaluation: true
training:
  batch_size: 1000
  num_epochs: 3
  pipeline:
    sync: true
@griii griii added the question Further information is requested label Mar 15, 2024
@zosong
Copy link

zosong commented Jul 15, 2024

I have the same problem with the same storage set-up. When I set the PARTITION_BUFFER, there will be a seg fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants