Re: [Cocci] Checking import of code search results into a table by parallel SmPL data processing
> Since you haven't included the semantic patch, This information can become useful later eventually. > it seems that there is no way anyone can help you. Other developers can provide also helpful advices. Example: Mike Bayer Topic: Checking approaches around parallel data import for records https://groups.google.com/d/msg/sqlalchemy/5-6O-Pwzh4A/5xSnxE_pDAAJ See also: https://docs.sqlalchemy.org/en/13/core/connections.html#engine-disposal I am curious if more extensions will evolve for affected software areas. Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] Checking import of code search results into a table by parallel SmPL data processing
>> elfring@Sonne:~/Projekte/Linux/next-patched> time spatch --timeout 34 -j 2 >> --chunksize 1 -D database_URL=postgresql+psycopg2:///parallel_DVB_duplicates >> --dir drivers/media/dvb-frontends --sp-file >> ~/Projekte/Coccinelle/janitor/list_duplicate_statement_pairs_from_if_branches4.cocci >> > >> ~/Projekte/Bau/Linux/scripts/Coccinelle/duplicates1/next/20190418/pair-DVB-results.txt >> 2> >> ~/Projekte/Bau/Linux/scripts/Coccinelle/duplicates1/next/20190418/pair-DVB-errors.txt > > Since you haven't included the semantic patch, I intentionally omitted this implementation detail for the beginning of another discussion. > it seems that there is no way anyone can help you. I imagine that a possible system clarification will depend on the willingness to check parallel SmPL data processing (together with a class library like “SQLAlchemy 1.3.2”) once more. I am curious on how the development interests will evolve in such software areas. Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
[Cocci] Checking import of code search results into a table by parallel SmPL data processing
Hello, I have noticed another questionable software behaviour during the application of the semantic patch language. elfring@Sonne:~/Projekte/Linux/next-patched> time spatch --timeout 34 -j 2 --chunksize 1 -D database_URL=postgresql+psycopg2:///parallel_DVB_duplicates --dir drivers/media/dvb-frontends --sp-file ~/Projekte/Coccinelle/janitor/list_duplicate_statement_pairs_from_if_branches4.cocci > ~/Projekte/Bau/Linux/scripts/Coccinelle/duplicates1/next/20190418/pair-DVB-results.txt 2> ~/Projekte/Bau/Linux/scripts/Coccinelle/duplicates1/next/20190418/pair-DVB-errors.txt real5m56,708s user11m4,775s sys 0m0,688s I know from my previous update suggestion “[media] Use common error handling code in 19 functions” that change possibilities can be found. https://lkml.org/lkml/2018/3/9/823 https://lore.kernel.org/lkml/57ef3a56-2578-1d5f-1268-348b49b0c...@users.sourceforge.net/ But the generated log file contains the information “No result for this analysis!”. I wonder then why desired data were not stored in the corresponding database table by such a SmPL script variant. Is there still a need to perform parallelisation for the mentioned software components by other approaches? Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
